Project

General

Profile

Bug #138

libcharon: eap-simaka-pseudonym and eap-simaka-reauth conflict

Added by Stefan Tomas about 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Category:
libcharon
Target version:
Start date:
01.09.2011
Due date:
Estimated time:
Affected version:
4.5.3
Resolution:

Description

In our testing we have noticed that if both pseudonym and reauth plugins are enabled then server sends only reauth identity to the client during full EAP-SIM authentication. It should send both AT_NEXT_PSEUDONYM and AT_NEXT_REAUTH_ID attributes.

History

#1 Updated by Tobias Brunner about 9 years ago

  • Status changed from New to Resolved
  • Assignee set to Tobias Brunner
  • Target version set to 4.6.0

Thanks for the report. Should be fixed with 4b7c63cf.

Regards,
Tobias

#2 Updated by Tobias Brunner almost 9 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF