Date: Wed, 12 Oct 2005 17:39:46 +1000 From: Timothy Smith <timothy@open-networks.net> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-05:21.openssl Message-ID: <434CBDC2.4070405@open-networks.net> In-Reply-To: <434BBF09.6040101@htnet.hr> References: <200510111202.j9BC2obf081876@freefall.freebsd.org> <1129036481.434bbac1720a6@webmail.boxke.be> <434BBF09.6040101@htnet.hr>
next in thread | previous in thread | raw e-mail | index | archive | help
jere wrote: > unfortunately, this is the dark side of FreeBSD security patch > management :) and I think also the main reason FreeBSD isn't so > widely deployed into enterprise environments. It's ok for hacking or > managing few boxes but try to imagine how to manage security on > hundreds of them this way. :( > > on the other side (bright side :) you can try to use unofficial and > often somewhat slowly updating solutions such as bsdupdate > (www.bsdupdates.com) or freebsd-update (from ports tree). > > currently, FreeBSD just don't have a mechanism to handle security > advisories in quick way. > > any suggestions/corrections ? > > j. > your totally right, even though i hate to admit it. stuff like having to make world is a nightmare when admining lots of machines. i can't afford to make world only to find something screwed up, stuff like that would cost me a lot of time i can't afford. the make world documents mentioning backing up your system. it fails to give any preffered methods or utilites for doing this. anyone got some input on that.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?434CBDC2.4070405>