As also suggested here I am attempting to drive radclient as a poor man's
proxy connection from a custom script.
Unfortunately attribute names are apparently case-sensitive and
the environment variables lose case information from their names.
When I pass an attribute without matching the case in the dictionary
exactly, radclient hangs up on me right away.
Ow. Is there a workaround for this -- any option to eliminate the
case sensitivity for attribute names? Or are there really conflicts
between attribute names when case sensitivity is absent?
My script could pull in the entire FreeRADIUS dictionary and do
its own case-insensitive matching to get back to the correct
attribute name, but that's getting pretty baroque. Or I could
go for a middle ground and define my own small case-mapping dictionary
of attributes that really show up in Windows mschap2 client requests.
That seems increasingly likely.
Also, the RADIUS RFC says that the order of attributes with the
same name must be preserved, and I'm pretty sure you can't have
duplicates with environment variables at all. Does this actually
come up as an issue in practice (multiple values for
framed-protocol, for instance)?
Thank you for any and all information!
--
Thomas Boutell
Boutell.Com, Inc.
http://www.boutell.com/
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
