Date: Thu, 9 Jan 2003 10:03:58 +0700 From: budsz <budsz@kumprang.or.id> To: horcy <apehaar@text-only.demon.nl> Cc: FreeBSD-Security <freebsd-security@freebsd.org> Subject: Re: [security-advisories@freebsd.org: FreeBSD Security Advisory FreeBSD-SA-02:44.filedesc] Message-ID: <20030109030358.GA53970@kumprang.or.id> In-Reply-To: <005201c2b735$5483aae0$0201a8c0@JOS> References: <20030108162158.GC48296@kumprang.or.id> <004101c2b732$89d59940$0201a8c0@JOS> <20030108163957.GA49337@kumprang.or.id> <005201c2b735$5483aae0$0201a8c0@JOS>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 08, 2003 at 05:45:19PM +0100, horcy wrote: >Yup. >But if you were planning to do a cvsup this week. >Why not do it now. >Saves you some time because the cvsup will contain the patch too ;) Yeah, everyday I'am to do cvsup via cron. :) BTW that bug only core right? I mean no remote exploit or something else? -- budsz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030109030358.GA53970>