On Tuesday 20 December 2005 16:54, rihad wrote:
Is there a security branch for the FreeBSD ports collection?
No, there isn't.
Let's say,
I installed FreeBSD 6.0 together with all needed -RELEASE ports/packages
(i.e., those on the CD). Running security/portaudit after a while
reveals that
Is there a security branch for the FreeBSD ports collection? Let's say,
I installed FreeBSD 6.0 together with all needed -RELEASE
ports/packages. Running security/portaudit after a while reveals that
some of the installed packages have vulnerabilities. Am I on my own to
go grab the fresh
On Mon, Dec 19, 2005 at 06:56:25PM +0400, rihad wrote:
Is there a security branch for the FreeBSD ports collection?
No, the ports tree is not branched at all.
Let's say,
I installed FreeBSD 6.0 together with all needed -RELEASE
ports/packages. Running security/portaudit after a while
Andrea Venturoli wrote:
rihad wrote:
FreeBSD only has a current port tree.
The port tree you call -RELEASE is simply current as it was at the
time the base OS was released.
Yes, wrong wording here. I was aware of that snapshot thing happening,
just lazy to go check www.freebsd.org for the
--On December 19, 2005 6:56:25 PM +0400 rihad [EMAIL PROTECTED] wrote:
Is there a security branch for the FreeBSD ports collection? Let's say,
I installed FreeBSD 6.0 together with all needed -RELEASE ports/packages.
Running security/portaudit after a while reveals that some of the
installed
Paul Schmehl wrote:
I'm not sure what you mean by suffering all the intricacies. Cvsup
will fetch all the ports that have updates (assuming you use the right
config - man is your friend), so you really don't have to do much except
launch cvsup (if you haven't already scheduled it routinely)
Is there a security branch for the FreeBSD ports collection? Let's say,
I installed FreeBSD 6.0 together with all needed -RELEASE ports/packages
(i.e., those on the CD). Running security/portaudit after a while
reveals that some of the installed packages have vulnerabilities. Am I
on my own to
