1 / 5

One-Time Password Specifications (OTPS): CryptoAPI

One-Time Password Specifications (OTPS): CryptoAPI. Gareth Richards, RSA Security OTPS Workshop, February 2006. Overview. Describes Microsoft CryptoAPI objects, procedures and mechanisms that can be used to retrieve OTPs

meir
Download Presentation

One-Time Password Specifications (OTPS): CryptoAPI

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. One-Time Password Specifications (OTPS): CryptoAPI Gareth Richards, RSA Security OTPS Workshop, February 2006

  2. Overview • Describes Microsoft CryptoAPI objects, procedures and mechanisms that can be used to retrieve OTPs • Intended to meet the needs of applications wishing to access connected OTP tokens in an interoperable manner • Intended to mirror the sister PKCS#11 document

  3. Intent is to follow the HMAC approach for CryptoAPI CryptAcquireContext gives handle to key container OTP algorithm given by key in the container CryptCreateHash gives handle to OTP hash object CryptSetHashParam sets the OTP parameters CryptHashData generates OTPs CryptGetHashParam retrieves the OTP value Principals of Operation CryptAcquireContext CryptCreateHash CryptSetHashParam CryptHashData CryptGetHashParam

  4. Recent Changes • Draft 5, published November 17 • Added text clarifying the fact that an application should use returned OTP_PARAMETERS in authentication requests. • Added a CRYPT_OTP_FORMAT OTP parameter to allow applications to determine the format of the returned OTP.

  5. Next Steps • Values for new manifest constants are only outstanding issue. • Unable to obtain Microsoft approval for OTP extensions to CryptoAPI • Two possibilities for discussion: • Withdraw document • Assigned values will not be safe • Assign values with caveat • Assigned values will not be sanctioned

More Related