On 04/12/15 13:08, Jouni Malinen wrote:
> On Fri, Dec 04, 2015 at 10:27:48AM +, Matt Caswell wrote:
>> EAP-FAST is very strange. Normally you know whether you are resuming a
>> session or not based on the session id returned from the server. However
>> that's not the case with EAP-FAST - you
On Fri, Dec 04, 2015 at 10:27:48AM +, Matt Caswell wrote:
> EAP-FAST is very strange. Normally you know whether you are resuming a
> session or not based on the session id returned from the server. However
> that's not the case with EAP-FAST - you have to wait to see what message
> the server s
On 03/12/15 23:09, Jouni Malinen wrote:
> Any idea what happened with these OpenSSL client state machine changes
> and how to get this fixed to restore EAP-FAST functionality?
EAP-FAST is very strange. Normally you know whether you are resuming a
session or not based on the session id returned f
It looks like the new client TLS state machine breaks the EAP-FAST peer
implementation in wpa_supplicant. Based on git bisect, the first commit
where this happens was this one:
commit 8723588e1b9a13511ffd7b806c73293120bc1f44
Implement Client TLS state machine
This swaps the implementa
