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

From: Colin Percival (colin.percival_at_wadham.ox.ac.uk)
Date: 06/08/04

  • Next message: Kyle Mott: "RE: FreeBSD Security Advisory FreeBSD-SA-04:12.jailroute"
    Date: Tue, 08 Jun 2004 11:18:34 +0100
    To: freebsd-security@freebsd.org
    
    

    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-security@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-security
    To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"


  • Next message: Kyle Mott: "RE: FreeBSD Security Advisory FreeBSD-SA-04:12.jailroute"

    Relevant Pages

    • RE: Portinstall problem (config.guess not found)
      ... Freebsd ... The first port I try to to install is generally CVSUP. ... >> Attempting to fetch from ... *** Error code 1 ...
      (freebsd-questions)
    • Re: "sh -i" My server was hacked. How can i found hole on my server?
      ... Then make a clean install from disc. ... Check You FreeBSD version in uname -a. ... upgraded to the appropriate security branch? ... look for security advisories on the project ...
      (FreeBSD-Security)
    • unable to install Passivetex
      ... I am unable to install the Passivetex application. ... with FreeBSD 4.9 as well as with FreeBSD 5.1. ... unable to fetch ...
      (comp.unix.bsd.freebsd.misc)
    • Re: [freebsd-questions] Cant build php5?
      ... then installed IMP package with pkg_add -r imp. ... => Attempting to fetch from ... My goal here is to get a working FreeBSD 6.2 Horde/IMP server. ... easiest and fastest way to get a working install would be to ...
      (freebsd-questions)
    • Re: cvs commit: src/etc inetd.conf
      ... >> about security advisories is MUCH different ... It just won't save the experienced users any ... This is what FreeBSD 4.4 does with the inetd network services. ...
      (FreeBSD-Security)