Date: Wed, 13 Mar 2002 09:00:20 -0600 From: Eric Anderson <anderson@centtech.com> To: Andrew McNaughton <andrew@scoop.co.nz> Cc: batz <batsy@vapour.net>, Christopher Schulte <schulte+freebsd@nospam.schulte.org>, lewwid <lewwid@telusplanet.net>, freebsd-security@freebsd.org, Max Mouse <maxmouse@maxmouse.org> Subject: Re: Managing port security upgrades (was:Re: PHP 4.1.2) Message-ID: <3C8F6984.F90D02C@centtech.com> References: <20020313194713.A3633-100000@a2>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew McNaughton wrote: > > On Tue, 12 Mar 2002, batz wrote: > > Has anyone else done anything especially different for managing security > > specific patches? > > Rather than looking at separate distribution of ports, why not look at a > protocol for providing a list of versions of ports which are insecure. > This could be added into the daily security check. No remedy to problems > found, just notification. Something similar to the version checking > available through periodic at present except that it would only cover > security issues. > > Andrew McNaughton That would be pretty handy - as long as you could tell it "only look at installed ports" or "look at all ports", and other things like a way to tell it to exclude certain ports from checking. Eric -- ------------------------------------------------------------------ Eric Anderson Systems Administrator Centaur Technology If at first you don't succeed, sky diving is probably not for you. ------------------------------------------------------------------ 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?3C8F6984.F90D02C>