Date: Fri, 30 Jan 2004 16:21:11 +0000 From: Colin Percival <colin.percival@wadham.ox.ac.uk> To: security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-04:01.mksnap_ffs Message-ID: <6.0.1.1.1.20040130161508.03e79768@imap.sfu.ca> In-Reply-To: <200401301607.i0UG7CIl082205@freefall.freebsd.org> References: <200401301607.i0UG7CIl082205@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 16:07 30/01/2004, FreeBSD Security Advisories wrote: >============================================================================= >FreeBSD-SA-04:01.mksnap_ffs Security Advisory > >V. Solution >Do one of the following: > >1) Upgrade your vulnerable system to the RELENG_5_1 or RELENG_5_2 >security branch dated after the correction date. > >2) To patch your present system [...] As usual, there is a third option here: I'm building binary security updates and distributing them via the FreeBSD Update port (security/freebsd-update in the ports tree). For systems running an official RELEASE plus security patches, this provides an easier update method than building from source. To use these updates: 1) Install FreeBSD Update and copy the sample configuration file into place: # cd /usr/ports/security/freebsd-update && make install clean # cp /usr/local/etc/freebsd-update.conf.sample /usr/local/etc/freebsd-update.conf 2) Fetch and install updates: # /usr/local/sbin/freebsd-update fetch # /usr/local/sbin/freebsd-update install For more details see http://www.daemonology.net/freebsd-update/ . Note that this is something I'm providing personally; it is in no way endorsed by the Security Officer or the Project as a whole. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.1.1.1.20040130161508.03e79768>