Subject: Re: [eap] EAP failure: reasons?

From: "M. Vanderveen" <[email-masked]>
Date: Thu, 18 Jan 2007 19:22:39 -0800 (PST)

Even if they could find out from an errory type in the EAP failure message, that information cannot be trusted. EAP Failure as I understand it is rather catastrophic. In other abnormal circumstances (such as out-of-synch, method not acceptable) there are ways (method specific or EAP-specific) to at least inform the peer if not correct the problem.

In methods to date EAP Failure seems to be mandated upon signature/message protection failure detected at the server side, so this reason may be assumed as the most  common. If the peer is otherwise happy, then it must have disappointed the server with its (peer's) credentials :-)

Michaela

----- Original Message ----
From: Madjid Nakhjiri <[email-masked]>
To: [email-masked]
Sent: Thursday, January 18, 2007 5:39:42 PM
Subject: [eap] EAP failure: reasons?

Hi,
 
Question from implementers forwarded to the list:
 
EAP Failure and Success messages do not carry any Type or type data. This means the reason for Failure cannot be indicated to the peer using Failure packet.
Is it expected that the peer somehow within the EAP method finds out why things went wrong? 
Is there anyway to get around this?
 
Thanks in advance,
 
Madjid
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/eap

Arhives: http://lists.frascone.com/pipermail/eap

____________________________________________________________________________________
Have a burning question?  
Go to www.Answers.yahoo.com and get answers from real people who know.

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/eap

Arhives: http://lists.frascone.com/pipermail/eap