Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: FreeBSD Security Advisory FreeBSD-SA-04:12.jailroute

1 view
Skip to first unread message

colin.p...@wadham.ox.ac.uk

unread,
Jun 8, 2004, 6:19:12 AM6/8/04
to
At 22:06 07/06/2004, FreeBSD Security Advisories wrote:
>FreeBSD-SA-04:12.jailroute Security Advisory
>Affects: All FreeBSD 4.x releases prior to 4.10-RELEASE

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"

colin.p...@wadham.ox.ac.uk

unread,
Jun 8, 2004, 3:34:05 PM6/8/04
to
At 20:26 08/06/2004, Kyle Mott wrote:
>If we are running RELENG_4, will we still receive the fix? I ask because
>it says to upgrade to 4.10-RELEASE, RELENG_4_8, or RELENG_4_9. Am I
>misunderstanding the RELENG tags?

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.

0 new messages