hi - we're seeing a Lucent Stinger device sending radius requests with a
passowrd field that is less than the 16 octets as per protocol.
now, some radius servers seem not to like this - but freeradius seems to
work fine with this. i suspect that is because freeradius either ignores the
length of that field, or copies it to a zero-padded buffer.
am i right? see section of an email below for details...
tariq
-----
have the Password and Chap-Password fields with 16 and
17 octects respectively - as seen in the trace 5 logs. This is as per
protocol.
however, the problem stinger seems to send "short" passwords such as :
Password = "<249>!<19><31><236><170><172>"
Password = "<252><7><217><213><237><134><130>"
Password = "<249>!<19><31><236><170><172>"
and so on .. these are less than the normal:
Password = "<215>y<160><1>F<224><193><187>OM<'<0><222><197><227>"
- 16 octects
CHAP-Password =
<1><193><202>t<186><136><24><147><145><210>n<233>.{9!; - 17 octects
is this evidence that the problem lucent stinger is malforming its packets?
or are there valid cases when the Password field is short?
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
