-
Notifications
You must be signed in to change notification settings - Fork 4
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
Remove GMP dependency #3
Comments
a lot |
Getting rid of GMP is a very low priority goal for SQIsign. I should also point out that the SQIsign reference implementation is what the name indicates: an implementation for reference and absolutely not production-ready. |
Okay, thanks for the quick response. I'll close this for now, so you can reopen if it ever comes up again. I don't suppose you can give me a sense for any updates on standardization or review? |
NIST has indicated they intend to finalize the current round for additional signatures before the end of the year. Assuming that SQIsign passes the selection, we may do some tweaks to the specification, reflecting NIST's comments. So you may expect a new version by spring 2025, but no date is official. Speaking for myself, I have the impression that NIST is in no rush to standardize additional signatures, so you may have to wait several years before SQIsign becomes a standard. |
Thank you for the update! |
Hi, I'm looking to use SQIsign in Rust. I asked the maintainer of rustpq if they would be interested in including it, and they mentioned here that they won't merge any implementation with a GMP dependency:
rustpq/pqcrypto#65 (comment)
How difficult would this be to do?
The text was updated successfully, but these errors were encountered: