Date: Thu, 7 May 2009 06:58:18 +0200 From: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> To: freebsd-questions@freebsd.org Cc: Tim Judd <tajudd@gmail.com>, Kalle =?iso-8859-1?q?M=F8ller?= <kalle.moller@gmail.com> Subject: Re: Maintaining a FreeBSD system - Workcycle Message-ID: <200905070658.18661.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> In-Reply-To: <ade45ae90905062048o3028e8a5jd7c222ed63f9a5dd@mail.gmail.com> References: <8250ac3f0905061743l21a9a87fv9ca3aa50cb176873@mail.gmail.com> <ade45ae90905062048o3028e8a5jd7c222ed63f9a5dd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 07 May 2009 05:48:10 Tim Judd wrote: > 2) Install portaudit and watch the periodic mailings that are sent to you. > They list vulnerabilities in ports that really should be addressed. Not really. You can use the same common sense as with the base system and even more so (for the base system I just install them always, as it doesn't pay off in the long run to skip them). Portaudit for a (web)server has a lot of notifications that "are not critical", like several issues over the last year with php's safe mode that any sane webserver admin doesn't use. -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905070658.18661.mel.flynn%2Bfbsd.questions>