Use an ${OPSYS}-specific message file for DragonFly, to get the right

local security information.

With thanks to Joerg Sonnenberger for the DragonFly help, and Trevor
Kendall for the original report.

1 files changed, 23 insertions, 0 deletions

diff --git a/security/audit-packages/MESSAGE.DragonFly b/security/audit-packages/MESSAGE.DragonFly
new file mode 100644
index 00000000000..78f70358f0f
--- /dev/null
+++ b/security/audit-packages/MESSAGE.DragonFly
@@ -0,0 +1,23 @@
+===========================================================================
+$NetBSD: MESSAGE.DragonFly,v 1.1 2005/12/29 23:47:55 agc Exp $
+
+You may wish to have the vulnerabilities file downloaded daily so that
+it remains current.  This may be done by adding an appropriate entry
+to the root users crontab(5) entry.  For example the entry
+
+# download vulnerabilities file
+0 3 * * * ${PREFIX}/sbin/download-vulnerability-list >/dev/null 2>&1
+
+will update the vulnerability list every day at 3AM. You may wish to do
+this more often than once a day.
+
+In addition, you may wish to run the package audit from the daily
+security script.  This may be accomplished by adding the following
+lines to /etc/period/security/NNN.audit-packages, where NNN is a
+number specifying the order of execution.
+
+if [ -x ${PREFIX}/sbin/audit-packages ]; then
+        ${PREFIX}/sbin/audit-packages
+fi
+
+===========================================================================