eap-ttls/mschapv2 versus eap-peap/mschapv2 behaviour

[Phil Mayers]

On 18/07/13 10:56, Olivier Beytrison wrote:

> Now I like the short-circuit concept as it save quite some uneeded
> processing. But I'd like to have a mechanism that remove and stores any
> attributes present in the reply (within the inner-tunnel) until the
> mschapv2 succeeded.

Ok. What, in detail, are you proposing?

For clarity - I think it would be a mistake for the server core to save 
all attributes from Access-Challenge and copy them to the Access-Accept; 
it would *have* to be smarter/more conditional than that, and I would 
want a way to disable it.