Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Providing a context parameter for signature operations #240

Open
athoelke opened this issue Feb 7, 2025 · 0 comments
Open

Providing a context parameter for signature operations #240

athoelke opened this issue Feb 7, 2025 · 0 comments
Labels
Crypto API Issue or PR related to the Cryptography API enhancement New feature or request

Comments

@athoelke
Copy link
Contributor

athoelke commented Feb 7, 2025

Up to now, the API does not have a context parameter in signature functions, although a number of signature schemes are defined with a context. This was partly due to there being no use cases in standards for the context parameter, for the signature algorithms included in the API specification (just EdDSA in v1.2).

The recently standardized FIPS post-quantum signature algorithms, ML-DSA and SLH-DSA, also include a context parameter.

The IETF draft proposal for hybrid signatures using ML-DSA (see https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-sigs/), is using a non-empty ML-DSA context parameter.

This suggests that it is time to provide sign-with-context and verify-with-context functions to the API. This should probably all 4 variations of psa_{sign|verify}_{message|hash}_with_context().

@athoelke athoelke added Crypto API Issue or PR related to the Cryptography API enhancement New feature or request labels Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Crypto API Issue or PR related to the Cryptography API enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant