Leon Dorfman <[EMAIL PROTECTED]> wrote:
> ATTRIBUTE Expiration 21 date
>
> It seems to me this is inconsistency, isn’t it?
No. The 'date' handling code reads it from the 'users' file as a
string, and sends it out on the wire as an integer date.
You really don't want to tpye 91736191 for the date, do you?
Anyways, I've fixed the bug. The date/string issue wasn't the
problem. It was that the Expiration attribute SHOULD be a server
attribute. Also, the code wasn't doing what you expected.
I bet if you tried something like:
bob Auth-Type := Local, Password == "bob", Expiration < "10 August 2001"
Reply-Message = "Yes!"
Then it would work. But it doesn't make much sense. So we can
either re-name the attribute, or change the way it behaves. I chose
to change the way it behaves.
bob Auth-Type := Local, Password == "bob", Expiration == "10 August 2001"
Reply-Message = "yes!"
Now means "On August 10, the user's account expires, so don't
let them in any more".
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
