Date: Thu, 18 Apr 2002 14:42:06 -0600 From: Brett Glass <brett@lariat.org> To: Ken McGlothlen <mcglk@artlogix.com> Cc: Christopher Schulte <schulte+freebsd@nospam.schulte.org>, security@FreeBSD.ORG Subject: Re: FreeBSD Security Advisory FreeBSD-SA-02:21.tcpip Message-ID: <4.3.2.7.2.20020418143615.021a8460@nospam.lariat.org> In-Reply-To: <87r8lcakpt.fsf@ralf.artlogix.com> References: <4.3.2.7.2.20020418095356.024354c0@nospam.lariat.org> <4.3.2.7.2.20020417230144.032ad390@nospam.lariat.org> <200204171923.g3HJNga58899@freefall.freebsd.org> <4.3.2.7.2.20020418095356.024354c0@nospam.lariat.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 01:08 PM 4/18/2002, Ken McGlothlen wrote: >Actually, it's not as bad as it might seem. I suspect what's got you upset is >the thought of having to do a make buildworld on every machine. I can tell you >how to avoid that.... [Snip] Good tips here, assuming that you're willing to keep a build server around. But what if you're doing a fresh install at a customer site (with Internet feed), and want to get from floppies to a reasonably secure system without headaches? Also, won't "make installworld" nuke some of the customization you've done to each machine? And what if you're running with SECURELEVEL=2 on your production servers? --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20020418143615.021a8460>