-
Notifications
You must be signed in to change notification settings - Fork 469
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
Comments
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. |
Closing as this is superseded by #1894. |
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.
The text was updated successfully, but these errors were encountered: