Sam Hartman wrote:
> Hi. As we're starting to gain implementation experience, it looks like
> this is a real problem with a lot of implementations out there. The
> server we're looking at just sends back an EAP success packet
> (unencrypted) as soon as it's sure that you've reached a success stat
> "Sam" == Sam Hartman writes:
Sam> Hi.
Sam> EAP has a complex history of success indications over the
Sam> years. Some methods have protected success indications; some
Sam> don't.
Sam> Especially as channel bindings are being initially deployed
Sam> it's going to
Hi.
EAP has a complex history of success indications over the years.
Some methods have protected success indications; some don't.
Especially as channel bindings are being initially deployed it's going
to be common to want to send channel bindings and possibly fail if they
do not match but not