PSA Certified
Crypto API 1.2 PAKE Extension

Document number:	AES 0058
Release Quality:	Final
Issue Number:	1
Confidentiality:	Non-confidential
Date of Issue:	28/03/2024

FINAL RELEASE

This is an extension to the PSA Certified Crypto API [PSA-CRYPT] specification.

This is a FINAL release: the proposed changes and interfaces are complete and finalized, and suitable for product development.

Abstract

This document is part of the PSA Certified API specifications. It defines an extension to the Crypto API, to introduce support for Password-authenticated key exchange (PAKE) algorithms.

Contents

• About this document
  • Release information
  • License
  • References
  • Terms and abbreviations
  • Potential for change
  • Conventions
  • Current status and anticipated changes
  • Feedback

• 1. Introduction
  • 1.1. About Platform Security Architecture
  • 1.2. About the Crypto API PAKE Extension
  • 1.3. Objectives for the PAKE Extension
    • 1.3.1. Scheme review
    • 1.3.2. Scope of the PAKE Extension
• 2. Password-authenticated key exchange (PAKE)
  • 2.1. Common API for PAKE
    • 2.1.1. PAKE algorithms
    • 2.1.2. PAKE primitives
    • 2.1.3. PAKE cipher suites
    • 2.1.4. PAKE roles
    • 2.1.5. PAKE step types
    • 2.1.6. Multi-part PAKE operations
    • 2.1.7. PAKE support macros
  • 2.2. The J-PAKE protocol
    • 2.2.1. J-PAKE cipher suites
    • 2.2.2. J-PAKE password processing
    • 2.2.3. J-PAKE operation
    • 2.2.4. J-PAKE algorithms
  • 2.3. The SPAKE2+ protocol
    • 2.3.1. SPAKE2+ cipher suites
    • 2.3.2. SPAKE2+ registration
    • 2.3.3. SPAKE2+ operation
    • 2.3.4. SPAKE2+ keys
    • 2.3.5. SPAKE2+ algorithms
• 3. Algorithm and key type encoding
  • 3.1. Algorithm encoding
    • 3.1.1. PAKE algorithm encoding
  • 3.2. Key encoding
    • 3.2.1. SPAKE2+ key encoding

• A. Example header file
  • A.1. psa/crypto.h
• B. Example macro implementations
• C. Changes to the API
  • C.1. Document change history
    • C.1.1. Changes between Final and Final.1
    • C.1.2. Changes between Beta 1 and Final
    • C.1.3. Changes between Beta 0 and Beta 1