As far as I know none of the rfc updating 2865 redefine the class attribute.
Is there a reason for this, is it safe to make it a string value?
I very much suggest leaving it alone. Editing things just to make the
"closer" to the RFC's is not a good idea. The RFC's are well known to
be wrong in many cases.
One point of (probably minor) interest; we changed it to be "string"
here, because it allowed us to get readable text in SQL queries.
i.e. before we had:
insert into blah ... '%{Class}'
...expanding to:
insert into blah ... '0xTHEHEX'
...and if it's a string we get:
insert into blah ... 'thestring'
...but that only works because we *know* that we're putting readable
strings into Class everywhere.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
