include_length and EAP-TTLS

[Gong Cheng]

(sorry i still don't know how to reply into a thread from yahoo web mail)
Yeah I agree. All the supplicants I used are ok with that. I just thought I might point it out ... Thanks for your reply Alan.





Re: include_length and EAP-TTLS
________________________________
 
	* To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org>
	* Subject: Re: include_length and EAP-TTLS
	* From: Alan DeKok <aland at deployingradius.com>
	* Date: Fri, 05 Dec 2008 07:58:14 +0100
	* In-reply-to: <542789.4743.qm at web82103.mail.mud.yahoo.com>
	* References: <542789.4743.qm at web82103.mail.mud.yahoo.com>
	* Reply-to: FreeRadius users mailing list <freeradius-users at lists.freeradius.org>
	* User-agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
________________________________
 
Gong Cheng wrote:
> I wonder if this is a small violation of the EAP-TTLS RFC (5281).
> 
> In RFC 5281 http://tools.ietf.org/html/rfc5281#section-9.2.2, it states:
> 
> "  .... Fragments other than the first MUST NOT have the L
>    bit set. ...
> "
> 
> while this behavior is configurable in eap.conf:
...
> I confess that I only actually SEE the behavior in the now ancient 1.1.6 version, and only took a quick look at the 2.1.0 config file and source code. I apologize if  I missed something or this had been brought up before.

  I don't think it's serious.  I don't know why this is a MUST NOT,
because it makes very little difference to the protocol.  And
supplicants that break if the L bit is set on second fragments are badly
written.

  Alan DeKok.