1 / 6

55th IETF Atlanta, GA, November 17-21, 2002 “EAP support in smartcards”

55th IETF Atlanta, GA, November 17-21, 2002 “EAP support in smartcards”. My name is Pascal Urien urienp@wifisecurity.org. Draft-urien-EAP-smartcard-00.txt. Draft Overview. Smartcard. Supplicant. Authenticator. RADIUS server. EAP. EAP / 7816. EAP / LAN. EAP / RADIUS. ISO 7816. 802.1x.

Download Presentation

55th IETF Atlanta, GA, November 17-21, 2002 “EAP support in smartcards”

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 55th IETFAtlanta, GA, November 17-21, 2002“EAP support in smartcards” My name is Pascal Urien urienp@wifisecurity.org Draft-urien-EAP-smartcard-00.txt

  2. Draft Overview Smartcard Supplicant Authenticator RADIUS server EAP EAP / 7816 EAP / LAN EAP / RADIUS ISO 7816 802.1x RADIUS • Secure Authentication • User authentication rather than computer authentication.

  3. Draft Objectives. • EAP support in smartcards. • EAP is computed in smartcard. • Profiles definition, for some EAP types (EAP-SIM, EAP-TLS, …) • Interoperability between ISO 7816 EAP smartcards. • Agreement between major smartcard manufacturers. • Four service primitives. • Get-Next-identity() • Set-Identity() • EAP-Packet() • Get-RSN-Master-Key() EAP ENGINE MD5 EAP SIM IAK KERB EAP AKA EAP TLS EAP Smartcard

  4. Draft content. Defines 4 services primitives associated to four APDUs and two informative profiles. • EAP-SIM • EAP-MD5 4 Services, shuttled by 4 APDUs. • Get_Next_Identity() • CLA=A0 INS=16 P1=01 P2=00 Lc=0 Le=xx • Set_Identity() • CLA=A0 INS=16 P1=80 P2=00 Lc=xx Le=00 • EAP_Packet() • CLA=A0 INS=80 P1=00 P2=00 Lc=xx Le=yy • Get_RSN_Master_key() • CLA=A0 INS=A6 P1=00 P2=00 Lc=00 Le=16.

  5. System Identity Concept • A wireless user may have several (EAP) identity associated to various 802.11 networks. The system identity is an ASCII string pointed to a particular (EAP) identity. The draft suggest three identity types, • The network SSID as described in the 802.11 standard . • The NAI , the network realms and user name. • A user’s identification (UID) e.g. an ASCII string, for example a friendly name. • Get-Next-Identity() • Returns an identity from a circular list. • Set-Identity() • Sets the smartcard identity, e.g everything required for EAP packet computing. • The triplet (EAP-Identity, EAP-Type, Key(s)).

  6. EAP Support. • EAP_Packet() • EAP-Packet() processes an EAP (request) message an returns an EAP (response) message. • Get_RSN_Master_Key() • Returns the session master key, if any, deduced from a successful authentication scenario. Secure Trusted EAP Engine In Out Master_Key

More Related