As a few people have noted, this should read "FreeBSD 4.8 and 4.9"; this bug
never existed in earlier versions of FreeBSD.
That said, FreeBSD 4.7 and earlier are no longer officially supported, and it
is highly recommended that people upgrade to a newer version, since there have
been recent security advisories concerning issues to which earlier releases are
still vulnerable.
>V. Solution
>Do one of the following:
>
>1) Upgrade your vulnerable system to 4.10-RELEASE, or to the RELENG_4_8
>or RELENG_4_9 security branch dated after the correction date.
>
>OR
>
>2) Patch your present system:
or, as usual,
3) If you are running an affected release, you can use FreeBSD Update:
# cd /usr/ports/security/freebsd-update && make all install
# cp /usr/local/etc/freebsd-update.conf.sample /usr/local/etc/freebsd-update.conf
# /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
_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-securi...@freebsd.org"
This was fixed in RELENG_4 in April:
>Corrected: 2004-04-06 20:11:53 UTC (RELENG_4)
So yes, if you upgrade to the latest -STABLE now, this problem will be
fixed.