Skip to content

Conversation

@pamaury
Copy link
Contributor

@pamaury pamaury commented Dec 3, 2025

Backport #25857

I typo'ed the formal sphincs+ algorithm names as `SLA-DSA-...` when they
should have been `SLH-DSA-...`.

Signed-off-by: Chris Frantz <[email protected]>
(cherry picked from commit 2df0158)
Rename the `spxef` module to `extra::spxef` as we'll be adding more
custom backends into the `extra` module.

Signed-off-by: Chris Frantz <[email protected]>
(cherry picked from commit 9603e67)
@pamaury pamaury requested a review from a team as a code owner December 3, 2025 14:45
@pamaury pamaury requested review from a team, AlexJones0, cfrantz, jwnrt and timothytrippel and removed request for a team December 3, 2025 14:45
Copy link
Contributor

@jwnrt jwnrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I didn't check against the API but the code looks okay and matches the backport so fine with me.

Signed-off-by: Chris Frantz <[email protected]>
(cherry picked from commit 454909f)
Some HSMs perform the domain preparation as part of their API, and thus
we should not perform domain preparation on the data sent to the HSM.

1. Remove domain prepration from the `SignData` preparation function.
2. Add domain preparation to the acorn backend.
3. Pass the domain parameter to the sphincsplus reference implementation
   sign/verify functions.

Signed-off-by: Chris Frantz <[email protected]>
(cherry picked from commit e7ef7f5)
1. Use the CloudKMS REST/json API to perform SPHINCS+ signing.

Signed-off-by: Chris Frantz <[email protected]>
(cherry picked from commit 2ce2a91)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants