Hello All,
I'm using Radiator on Windows 95 with only a handful of users -
more of a test system than fully blown production. We are happy
with things as they stand but superiors have asked me questions
I can't answer and so I wonder if anyone can help.
Am I right in thinking that password expiry would work naturally
if I moved to NT or Unix and used the system password files rather
than the flat file I'm using now?
Can Radiator be configured to warn of imminent password expiry using the
Reply-Message attribute?
Is there any way in which users can change their passwords 'on the fly'?
My reading of rfc2138 tells me that the concept doesn't fit very well with
the Radius protocol unless Vendor-Specific attributes are used.
I would be very interested to hear from anyone doing this - before or after expiry.
I see that Microsoft appears to allow the Chap-Password to be changed after expiry -
http://search.ietf.org/internet-drafts/draft-ietf-pppext-mschap-v2-03.txt
http://www.rfc-editor.org/rfc/rfc2548.txt
Does Radiator understand any Vendor-Specific codes or is it transparent
to them all?
That's enough questions to be going on with :)
Thanks in advance.
Arnie
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
