From 9c79412b3500bea5f0d5ae77fa3b06f37443ca11 Mon Sep 17 00:00:00 2001 From: Remko Lodder Date: Fri, 17 Mar 2006 11:51:15 +0000 Subject: [PATCH] Remove the chapter about "If VuXML still scares you". We do no longer encourage people to use this approach. This will be the start of cleaning up the VuXML/portaudit information. Discussed with: simon --- .../books/porters-handbook/book.sgml | 27 ------------------- 1 file changed, 27 deletions(-) diff --git a/en_US.ISO8859-1/books/porters-handbook/book.sgml b/en_US.ISO8859-1/books/porters-handbook/book.sgml index a65991e4db..24687f2a0a 100644 --- a/en_US.ISO8859-1/books/porters-handbook/book.sgml +++ b/en_US.ISO8859-1/books/porters-handbook/book.sgml @@ -7162,33 +7162,6 @@ Reference: <http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00 &prompt.user; packaudit &prompt.user; lynx ~/public_html/portaudit/74a9541d-5d6c-11d8-80e3-0020ed76ef5a.html - - - If VuXML still scares you... - - As an easy alternative to writing VuXML, you may opt to add - a single line to a different file with much simpler syntax, - PORTSDIR/security/portaudit-db/database/portaudit.txt, - which resides within the port security/portaudit-db, and - send a request for review to the Security Officer Team - as described on the FreeBSD - Security Information page. - - A line in that file consists of four fields - separated by |, a pipe character. - The first field is a &man.pkg.version.1; pattern - expression matching the vulnerable packages. The second - field contains URLs to relevant information, separated - by space characters. The third field is a one-line - description of the issue. The fourth and last field - is the entry's UUID. - - You may want take a closer look at existing entries in - portaudit.txt before adding your - first line to that file. -