getting around SASL

[Carter Bullard]

Hey Russell,
Good to see you among the living !!!

What about your ~/.rarc file.  It could have these values set as well.  If it is still a mystery, turn on "-D 5" or something close, and we should see the sasl mechanisms debug info.
Carter


On Mar 29, 2012, at 1:57 PM, Russell Fulton <r.fulton at auckland.ac.nz> wrote:

> HI Carter,  It's been a while :)
> 
> On 28/03/2012, at 12:06 PM, Carter Bullard wrote:
> 
>> Hey Russell,
>> The option should be "-M sasl_mech='none' ", not "-m ….".  The -m option is
>> to specify the flow aggregation key.
> 
> right you are!
> 
>> 
>> What error do you get with you don't specify anything on the command line?
> 
> [rful011 at mon263595 ~]$ ratop  -S localhost
> ArgusError: 06:48:25.083032 RaSaslNegotiate: error starting SASL negotiation SASL(-4): no mechanism available: No worthy mechs found
> 
> [rful011 at mon263595 ~]$ ratop -M sasl_mech='none' -S localhost
> ArgusError: 06:45:13.082264 RaSaslNegotiate: error starting SASL negotiation SASL(-4): no mechanism available: No worthy mechs found
> 
> [rful011 at mon263595 ~]$ ps ax | grep argus
>  455 ?        Rs     0:04 /usr/sbin/argus -F /home/argus/config/argus
>  459 pts/2    S+     0:00 grep argus
> 
> [rful011 at mon263595 ~]$ grep SSF /home/argus/config/argus
> ARGUS_MIN_SSF=0 ARGUS_MAX_SSF=0
> 
> 
> 
>> 
>> Argus or radium dictate the protection strategy on the connection.
>> You need to satisfy them to get data from them.  If you can't get an algorithm
>> on the client end, you'll have to get the argus or radium configuration
>> changed.
> 
> understood -- I assume that setting min and max to zero allows no auth.
> 
> THanks, Russell