George C. Kaplan wrote:
Phil Mayers wrote:
I'll try to give an example. Suppose you had two entries, using '=='
for the same user:
plong Auth-Type = Local, User-Password == "126"
plong Auth-Type = Local, User-Password == "123"
Then, if 'plong' supplies the password "123", the 'files' mod
Phil Mayers wrote:
>> I'll try to give an example. Suppose you had two entries, using '=='
>> for the same user:
>>
>> plong Auth-Type = Local, User-Password == "126"
>>
>> plong Auth-Type = Local, User-Password == "123"
>>
>> Then, if 'plong' supplies the password "123", the 'files' module
>>
I'll try to give an example. Suppose you had two entries, using '=='
for the same user:
plong Auth-Type = Local, User-Password == "126"
plong Auth-Type = Local, User-Password == "123"
Then, if 'plong' supplies the password "123", the 'files' module (which
processes the 'users' file) will
Paul Long wrote:
Basically, := is a "force set" operator. In a "check" item, it sets a
check/config pair.
So "Always matches a check item" just means that a check will be
performed and says nothing about the outcome of that check?
check items == config items. config items == attribute/valu
On Jul 21, 2006, at 6:31 PM, Paul Long wrote:
Phil Mayers wrote:
Paul Long wrote:
A man page (http://www.die.net/doc/linux/man/man5/users.5.html)
for the users file says, "Attribute := Value ... Always matches
as a check item..." So does that mean, no matter what the value
is, it will al
login attempt by "plong" with CHAP password
rlm_chap: Using clear text password 123 for user plong authentication.
rlm_chap: chap user plong authenticated succesfully
Yes...
In fact, := behaves exactly like == in this case. What's the deal?
Why doesn't := "always mat
ch, I have to have the correct value:
plongAuth-Type = Local, User-Password := "123"
which results in this debug output:
rlm_chap: login attempt by "plong" with CHAP password
rlm_chap: Using clear text password 123 for user plong authentication.
rlm_chap: chap user plon
al, User-Password := "123"
which results in this debug output:
rlm_chap: login attempt by "plong" with CHAP password
rlm_chap: Using clear text password 123 for user plong authentication.
rlm_chap: chap user plong authenticated succesfully
In fact, := behaves exactly
8 matches
Mail list logo