sasl support for argus and clients

[carter at qosient.com]

Hey Gabriel,
The design is that the variables in the argus.conf should dictate what the min and max security levels should be.
I believe there is a default non-zero value, so if you compiled in sasl support, and you don't want security, you should set the *SSL_MIN* and *SSL_MAX* to zero?

Carter

Carter Bullard
QoSient LLC
150 E. 57th Street Suite 12D
New York, New York 10022
+1 212 588-9133 Phone
+1 212 588-9134 Fax  

-----Original Message-----
From: "Gabriel L. Somlo" <somlo at cmu.edu>
Date: Tue, 18 Jul 2006 17:40:59 
To:Carter Bullard <carter at qosient.com>
Cc:Argus <argus-info at lists.andrew.cmu.edu>
Subject: Re: [ARGUS] sasl support for argus and clients

On Mon, Jul 17, 2006 at 11:32:23PM -0400, Carter Bullard wrote:
> A new set of release candidates is now available on the server.
> This set enables SASL support for strong encryption and authentication
> for argus and its clients.   This release is intended for those that are
> doing SASL testing (although anyone is welcome to test), as you need
> to create sasl accounts on the machine running argus (saslpasswd),
> so there is some work to do just to get started.

Carter,

I built both argus rc.20 and argus-clients rc.21 on FC4 (using
--with-sasl=yes) , and whenever I try to run ra to connect to argus,
I get this:


ra -n -S 128.2.4.35
ra[32280]: 17:33:27.932784 RaSaslNegotiate: error starting SASL negotiation
Segmentation fault


I haven't set up any SASL accounts or changed anything in the config
file from the last set of release candidates.

Do you mean that when compiling with SASL support (--with-sasl or
--with-sasl=yes), SASL accounts then become *mandatory* ?

Thanks,
Gabriel