{"id":280,"date":"2005-11-03T20:22:40","date_gmt":"2005-11-03T19:22:40","guid":{"rendered":"http:\/\/wp.devco.net\/?p=280"},"modified":"2009-10-09T16:56:38","modified_gmt":"2009-10-09T15:56:38","slug":"portaudit_central_10","status":"publish","type":"post","link":"https:\/\/www.devco.net\/archives\/2005\/11\/03\/portaudit_central_10.php","title":{"rendered":"Portaudit Central 1.0"},"content":{"rendered":"

Portaudit<\/a> is intended to run daily against your ports directory identifying known vulnerabilities against a central database. Each night it produce an email that gets sent out and requires inspection.
\nThe problem with this is with many FreeBSD hosts the emails can just be too many and I tend not to look at them.
\nPortaudit Central provides a means for delivering portaudit output to a central email box which will then produce a simple HTML based report of all machines. You can view a Sample Report<\/a> produced using these scripts.
\nThe server side script will call logger(1) with some useful diagnostic messages but the lines being logged will include some variables from the environment. I developed this under exim and the environment variables it logs are set by Exim<\/a>. This will still work under another MTA, the worst that will happen is you’d have some logging entries thats missing details like the sender and message id.
\nI’ve taken some steps to prevent man-in-the-middle attacks. An attacker can in theory produce a report that says you have no vulnerabilities on a host when in fact you do have some. In order to combat this a few things are done:<\/p>\n