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

Decode FORS indices similarly to WOTS #1838

Closed
GillonB opened this issue Jul 10, 2024 · 2 comments
Closed

Decode FORS indices similarly to WOTS #1838

GillonB opened this issue Jul 10, 2024 · 2 comments

Comments

@GillonB
Copy link

GillonB commented Jul 10, 2024

Can we add coming changes to SPHINCS+ implementation to liboqs? Could be as a temporary branch as done in sphincs/sphincsplus#51.

This change breaks forward/backward compatibility between old/new signatures.

@dstebila
Copy link
Member

Thanks for bringing this to our attention and for starting a PR to make the changes! We would definitely want to update to match the eventually NIST standard.

Because it's a compatibility-breaking change, we would include this in a release incrementing the second version number (0.x.y to 0.x+1.0).

But there's a second consideration around compatibility-breaking changes. For Kyber / ML-KEM, because Kyber Round 3 had already seen significant deployment within TLS, we have both Kyber Round 3 and ML-KEM (FIPS-203-ipd) available in the library, at least for now. Is SPHINCS+ deployment sufficiently widespread that we would need to keep SPHINCS+ and this tweaked version both available in the library for some period of time? I hope not, but wanted to raise the possibility.

@SWilson4
Copy link
Member

Closing as this is superseded by #1894.

@github-project-automation github-project-automation bot moved this from Todo to Done in liboqs planning Sep 25, 2024
@SWilson4 SWilson4 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants