Ken Foskey wrote:
a) How do you ensure your 'master' is current with all the patches?
As one would with any Linux Kernel and application.
It would be interesting to be specific. How did you deal with the Debian
break-in for example? Did you have the AM patches in already or did you
include them and roll them out urgently?
Can't be specific for obvious reasons.
The Debian break-in is unfortunate (http://www.wiggy.net/debian/explanation).
Their access procedure is different as I can gather.
As an aside do you rely on kernel source trees or distribution source
trees. I use Debian source to build my firewall's kernel so I get the
benefit of any patching that debian may have done.
Again, can't be specific.
b) How do you ensure that your clients are updated to the revised copyThe important thing as always is management processes. Each client has their
on an ongoing process?
standard operating procedures that lets them update on a regular basis as well
as emergency basis.
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
