Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 6 Mar 2004 11:01:30 +0000
From:      Stacey Roberts <stacey@vickiandstacey.com>
To:        "Cordula's Web" <cpghost@cordula.ws>
Cc:        stacey@vickiandstacey.com
Subject:   Re: /usr/src/UPDATING vs FreeBSD Security Advisory FreeBSD-SA-04:04.tcp
Message-ID:  <20040306110130.GL359@crom.vickiandstacey.com>
In-Reply-To: <20040306105152.66A8940827@fw.farid-hajji.net>
References:  <20040306104838.GK359@crom.vickiandstacey.com> <20040306105152.66A8940827@fw.farid-hajji.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello,
     Thanks for the reply.

----- Original Message -----
From: "Cordula's Web <cpghost@cordula.ws>"
To: To stacey@vickiandstacey.com
Date: Sat, 06 Mar, 2004 10:51 GMT
Subject: Re: /usr/src/UPDATING vs FreeBSD Security Advisory FreeBSD-SA-04:04.tcp

> > I've just (with cvsup) started upgrading one of my boxes in
> > line with the recent advisory (FreeBSD Security Advisory
> > FreeBSD-SA-04:04.tcp), and I'm at the point where I am reading
> > /usr/src/UPDATING as per all recommendations from the HandBook
> > to various user group advisories.
> > 
> > Aren't details of this advisory (and others?) supposed to be in
> > /usr/src/UPDATING? I only askbecause I'd not want to proceed from
> > this point only to realise later on that the system *wasn't* patched
> > after all.
> 
> UPDATING is not the place for this. You'll have to check the
> revisions of the files manually against those in the advisory.
> 

Okay.., cheers for that. I appreciate your taking the time.

Regards,

Stacey

> -- 
> Cordula's Web. http://www.cordula.ws/
> 

-- 
Stacey Roberts
B. Sc (HONS) Computer Science

Web: www.vickiandstacey.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040306110130.GL359>