new code (rc.31) on the server

[Darren Spruell]

On 10/9/06, Carter Bullard <carter at qosient.com> wrote:
> Gentle people,
> New code uploaded on the server that corrects
> for a number of issues on the list.

Just to confirm building completes successfully on a recent OpenBSD, very clean.

Also, I'm not certain the protocol surrounding rc releases, just
noticed that the argus(8) manual documents the '-C <dir>' option for
chrooting and '-u <user>' for privilege revocation however 'argus
--help' still appears to give old help options.

I found a couple of misspellings of the word privilege also, if interested:

diff -Naur argus-3.0.0.rc.31.old/doc/FAQ argus-3.0.0.rc.31/doc/FAQ
--- argus-3.0.0.rc.31.old/doc/FAQ       Fri Aug 18 10:15:14 2006
+++ argus-3.0.0.rc.31/doc/FAQ   Mon Oct  9 19:50:17 2006
@@ -384,7 +384,7 @@
 10.2  Do I need to be root to run Argus?

       When run as a user program, if you intend to read packets
-      from a live interface, you will need to have root privledges
+      from a live interface, you will need to have root privileges
       to either open the device, or to put the interface in
       promiscuous mode.

diff -Naur argus-3.0.0.rc.31.old/man/man8/argus.8
argus-3.0.0.rc.31/man/man8/argus.8
--- argus-3.0.0.rc.31.old/man/man8/argus.8      Mon Sep 25 21:13:01 2006
+++ argus-3.0.0.rc.31/man/man8/argus.8  Mon Oct  9 19:50:55 2006
@@ -62,7 +62,7 @@
 .TP 5 5
 .BI \-C
 <dir>
-Specify a chroot directory to use after privlege access is complete.
+Specify a chroot directory to use after privilege access is complete.
 Must be super user to use this option.
 .TP 5 5
 .BI \-d
@@ -87,7 +87,7 @@
 .TP 5 5
 .B \-g
 <group>
-Specify a group name to change to after privlege access is complete.
+Specify a group name to change to after privilege access is complete.
 .TP 5 5
 .B \-h
 Print an explanation of all the arguments.
@@ -161,7 +161,7 @@
 .TP 5 5
 .B \-u
 <user>
-Specify an account name to change to after privlege access is complete.
+Specify an account name to change to after privilege access is complete.
 .TP 5 5
 .B \-U
 Specify the number of user bytes to capture.
diff -Naur argus-3.0.0.rc.31.old/support/Config/argus.conf
argus-3.0.0.rc.31/support/Config/argus.conf
--- argus-3.0.0.rc.31.old/support/Config/argus.conf     Mon Sep 25 20:52:23 2006
+++ argus-3.0.0.rc.31/support/Config/argus.conf Mon Oct  9 19:51:30 2006
@@ -155,7 +155,7 @@

 # Argus supports chroot(2) in order to control the file system that
 # argus exists in and can access.  Generally used when argus is running
-# with privleges, this limits the negative impacts that argus could
+# with privileges, this limits the negative impacts that argus could
 # inflict on its host machine.
 #
 # This option will cause the output file names to be relative to this
@@ -169,7 +169,7 @@

 # Argus can be directed to change its user id using the setuid() system
 # call.  This is can used when argus is started as root, in order to
-# access privleged resources, but then after the resources are opened,
+# access privileged resources, but then after the resources are opened,
 # this directive will cause argus to change its user id value to
 # a 'lesser' capable account.  Recommended when argus is running as
 # daemon.
@@ -182,7 +182,7 @@

 # Argus can be directed to change its group id using the setgid() system
 # call.  This is can used when argus is started as root, in order to
-# access privleged resources, but then after the resources are opened,
+# access privileged resources, but then after the resources are opened,
 # this directive can be used to change argu's group id value to
 # a 'lesser' capable account.  Recommended when argus is running as
 # daemon.
@@ -215,7 +215,7 @@
 # When Argus is configured to run as a daemon, with the -d
 # option, Argus can store its pid in a file, to aid in
 # managing the running daemon.  However, creating a system
-# pid file requires priviledges that may not be appropriate
+# pid file requires privileges that may not be appropriate
 # for all cases.
 #
 # When configured to generate a pid file, if Argus cannot

>
> Now headed to flocon 2006, in beautiful vancouver washington.
> If anyone is there, please be sure and say hi!!!!!!

Enjoy, gorgeous country up there.

-- 
Darren Spruell
phatbuckett at gmail.com