ARM-software/psa-api

Issues

• Define API for Stateless Hash-Based Digital Signature (SLH-DSA aka SPHINCS+)

  #97 opened a year ago by athoelke
  8

• Define API for Module-Lattice-Based Digital Signature (ML-DSA aka CRYSTALS-Dilithium)

  #96 opened a year ago by athoelke
  3

• Compatible reworking of asymmetric key type encoding

  #109 opened a month ago by athoelke
  4

• Should we add a 'since' tag to API elements?

  #208 opened 2 months ago by athoelke
  0

• Importing and exporting keys that are in non-default formats

  #149 opened 9 months ago by athoelke
  14

• Dragonfly PAKE for WPA3 use cases

  #203 opened 3 months ago by athoelke
  1

• Added flexibility for RSA PSS salt length

  #201 opened 3 months ago by gilles-peskine-arm
  0

• ECC key size for secp224k1 is not consistent with key size specification

  #200 opened 3 months ago by Emill
  1

• Support for interruptible key agreement/exchange

  #198 opened 5 months ago by athoelke
  8

• Custom methods for key generation and key derivation

  #167 opened 8 months ago by gilles-peskine-arm
  8

• crypto: MAX_SIZE constant for public key or key pair

  #180 opened 5 months ago by gilles-peskine-arm
  1

• Integrate the PAKE Extension into the Crypto API specification

  #170 opened 5 months ago by athoelke
  0

• Crypto API 1.2.1 : Review of Release Candidate

  #188 opened 6 months ago by athoelke
  1

• crypto: problematic specification of IV for PSA_ALG_CTR

  #181 opened 6 months ago by gilles-peskine-arm
  6

• Mistaken assumption in HMAC key definition and export format

  #183 opened 6 months ago by athoelke
  2

• Add support for the SRP-6/6a PAKE protocol

  #179 opened 7 months ago by athoelke
  1

• Problems combining PBKDF2 with a key agreement

  #172 opened 7 months ago by athoelke
  0

• Crypto PAKE Extension : Review of Release Candidate

  #141 opened 8 months ago by athoelke
  5

• Crypto API 1.2 : Review of Release Candidate

  #152 opened 8 months ago by athoelke
  1

• Secure Storage API 1.0.3 : Review of Release Candidate

  #136 opened 8 months ago by athoelke
  0

• Update to the PAKE API - should this remain a Beta?

  #93 opened 8 months ago by athoelke
  2

• Crypto 1.2 RC1 has not updated its description of the PAKE API

  #161 opened 8 months ago by athoelke
  0

• Ordering requirements/flexibility in PAKE operations

  #157 opened 8 months ago by athoelke
  4

• Define the export format for a SPAKE2+ key pair

  #153 opened 8 months ago by athoelke
  1

• Minor issues in the PAKE Extension Beta.2 release candidate 1

  #154 opened 8 months ago by athoelke
  0

• API support for DRBG

  #105 opened a year ago by ndevillard
  3

• Document date on title page of Crypto API v1.1.2 is incorrect

  #130 opened 9 months ago by athoelke
  0

• Crypto: soften the requirement for concurrency

  #134 opened 9 months ago by gilles-peskine-arm
  1

• Missing support for ‘out of band’ setup calculations in PAKE API

  #87 opened 9 months ago by athoelke
  3

• Overview of updates to the PAKE API

  #111 opened 9 months ago by athoelke
  1

• Use case review for Attestation API

  #133 opened 10 months ago by athoelke
  0

• Security Risk Assessment (SRA) for Attestation API

  #132 opened 10 months ago by athoelke
  0

• Add support for CMAC based KDF algorithms

  #106 opened 10 months ago by adeaarm
  25

• Key agreement interface may present the shared key material out of the secured space.

  #85 opened 10 months ago by tranvantruonggit
  10

• Return type for psa_pake_cs_get_hash() is wrong in Crypto API 1.1 PAKE Extension beta.1

  #121 opened 10 months ago by athoelke
  1

• It is impossible to derive multiple keys from the common secret in the PAKE API

  #86 opened 10 months ago by athoelke
  1

• APIs for extracting the shared secret from PAKE operations

  #100 opened 10 months ago by athoelke
  10

• PAKE SIZE macros need more arguments

  #88 opened 10 months ago by athoelke
  3

• The PAKE interface does not work easily with the Mbed TLS driver design

  #89 opened a year ago by athoelke
  7

• Should psa_key_derivation_verify_bytes be allowed with a USAGE_DERIVE secret?

  #113 opened a year ago by gilles-peskine-arm
  4

• Should a key derivation continue working after a verify failure?

  #112 opened a year ago by gilles-peskine-arm
  4

• ShangMi signature and asymmetric encryption algorithms (SM9)

  #108 opened a year ago by athoelke
  2

• Define API for Module-Lattice-based Key-Encapsulation Mechanism (ML-KEM aka Crystals-KYBER)

  #95 opened a year ago by athoelke
  4

• Use psa_key_derivation multipart operation for TLS 1.3 key

  #103 opened a year ago by qgrembertwitekio
  1

• Add API for RNG re-seeding

  #104 opened a year ago by ndevillard
  2

• Provide better description of multi-component updates

  #84 opened a year ago by athoelke
  0

• The limitation of a single active installation process is 'hidden' in the API reference

  #83 opened a year ago by athoelke
  0

• Confusing description of bootloader behavior when FAILED state is volatile

  #82 opened a year ago by athoelke
  0

• Use Explicit Context in the Crypto API.

  #77 opened a year ago by lhuang04
  1

• Provide example definitions for some of the implementation-defined macros

  #74 opened a year ago by athoelke
  0