Date: Sat, 3 Apr 2004 19:19:19 +0200 From: "Simon L. Nielsen" <simon@FreeBSD.org> To: "Jacques A. Vidrine" <nectar@FreeBSD.org>, Marc Fonvieille <blackend@FreeBSD.org>, doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/ports chapter.sgml Message-ID: <20040403171918.GG870@zaphod.nitro.dk> In-Reply-To: <20040403170558.GA81162@madman.celabo.org> References: <200404031621.i33GLXi0093774@repoman.freebsd.org> <20040403163003.GE870@zaphod.nitro.dk> <20040403170558.GA81162@madman.celabo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--hK8Uo4Yp55NZU70L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.04.03 11:05:58 -0600, Jacques A. Vidrine wrote: > On Sat, Apr 03, 2004 at 06:30:04PM +0200, Simon L. Nielsen wrote: > > > Isn't that a bit overkill? Ports that have security issues are marked > > FORBIDDEN so users can't install them. If people want extra securirty > > they can use portaudit which checks the vuxml databases automatically. > >=20 > > I also think it would be very hard to check vuxml manually in many > > cases, since ports can have a lot of dependencies, which might also > > contain security problems. >=20 > I haven't looked at the diff, but, it would probably be good to say more > or less: >=20 > Please check http://vuxml.freebsd.org/ for security issues, or you > can use portaudit to automate the checking for you. Yes, exactly the point I was trying (and probably failing) to make. --=20 Simon L. Nielsen FreeBSD Documentation Team --hK8Uo4Yp55NZU70L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAbvIWh9pcDSc1mlERAiBfAJ4lQUj9OIR0//TSwXa6iByrgPO79gCfSIGM aFBGOyT2htzcX69Js9IVUD8= =6XfS -----END PGP SIGNATURE----- --hK8Uo4Yp55NZU70L--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040403171918.GG870>