Re: [RadiusNT] malformed packet handling between RadiusNT 2.5.206

dsmith@kleintech.com
Wed, 2 Feb 2000 13:36:38 -0500

Do we now have options for types of malformed packets that are allowed?
malformed = 1 - ?
malformed = 2 - ?
malformed = 3 - "malformed passwords" ?

Could you provide what results these different values would produce?

"Dale E. Reed Jr." <daler@iea-software.com> on 02/02/2000 01:01:33 PM

Please respond to radiusnt@iea-software.com






To: radiusnt@iea-software.com

cc: (bcc: David L Smith/Klein)



Subject: Re: [RadiusNT] malformed packet handling between
RadiusNT 2.5.206 and 2.5.209

Josh Hillman wrote:
>
> What changed with "malformed packet" handling between RadiusNT 2.5.206 and
> 2.5.209?
> Everything works fine with 2.5.206, but as soon as I change the executable
> to 2.5.209 and restart the service, I get the following (debug=18)
> eventhough "AllowMalformed=1":

Set Malformed to 3. The RFC clearly says password data must be a
multiple
of 16. You'd be suprised how many people can't read an RFC, that write
RADIUS clients.

Ascend seems to send the password correctly sometimes, and incorrectly
other times.

--

Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com

For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart

For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart