View Single Post
  #4   (View Single Post)  
Old 2nd June 2013
shep shep is offline
Real Name: Scott
Arp Constable
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,507
Default

I do not have a NetBSD install at this time but typically the main server is mirrored.
I ftp'd the site (the url in FAQ is incorrect, it should be ftp://ftp.NetBSD.org/pub/pkgsrc/dist...ulnerabilities) and the file exits.
Quote:
9.14. Automated security checks

Please be aware that there can often be bugs in third-party software, and some of these bugs can leave a machine vulnerable to exploitation by attackers. In an effort to lessen the exposure, the NetBSD packages team maintains a database of known-exploits to packages which have at one time been included in pkgsrc. The database can be downloaded automatically, and a security audit of all packages installed on a system can take place. To do this, refer to the following two tools (installed as part of the pkgtools/pkg_install package):

pkg_admin fetch-pkg-vulnerabilities, an easy way to download a list of the security vulnerabilities information. This list is kept up to date by the pkgsrc security team, and is distributed from the NetBSD ftp server:

ftp://ftp.NetBSD.org/pkgsrc/distfile...ulnerabilities

pkg_admin audit, an easy way to audit the current machine, checking each known vulnerability. If a vulnerable package is installed, it will be shown by output to stdout, including a description of the type of vulnerability, and a URL containing more information.

Use of these tools is strongly recommended! After “pkg_install” is installed, please read the package's message, which you can get by running pkg_info -D pkg_install.

If this package is installed, pkgsrc builds will use it to perform a security check before building any package. See Section 5.2, “Variables affecting the build process” for ways to control this check.
It is possible that pkg-tools is not installed or your paths are incorrect. Can you provide # pkg_info | grep pkg
and # echo $PKG-PATH

Last edited by shep; 2nd June 2013 at 03:01 PM. Reason: correct cmd tag
Reply With Quote