eap Mailing List: Re: [Issue 248] Comments on EAP state machine v4

[John Vollbrecht (jrv]

--On Friday, July 16, 2004 12:22 PM -0400 Nick Petroni 
<npetroni [at] cs.umd.edu> wrote:
.
.
.

> > As a fall-back solution, I would recommend inserting something like the
> > following text advising that COND_SUCC may be dangerous:
> >
> > "In case the peer reaches the decision COND_SUCC, please note that the
> > peer is vulnerable to an active attacker that may easily lead him to
> > believe that the authenticator has reached any decision the attacker
> > chooses. In situations where security is a concern, it is RECOMMENDED to
> > avoid using the value COND_SUCC of the decision variable"
> This would be a good recommendation to method writers I think, but I am
> not sure a general claim about setting that variable alone is enough. We
> could add some guidelines for method authors in the Implementation
> Considerations section or perhaps better somewhere else? IMHO, the
> middle of the SM description is not the place to get into this.
I also think this would be a good recommendation, but not in the middle of 
the state machine.  Perhaps in a EAP methods document would be better.

> _______________________________________________
> eap mailing list
> eap [at] frascone.com
> http://mail.frascone.com/mailman/listinfo/eap