search

sphincs / sphincsplus

The SPHINCS+ reference code, accompanying the submission to NIST's Post-Quantum Cryptography project
https://sphincs.org
Other
131 stars 44 forks source link

Explain basic usage of most likely standard providing clear test vectors #35

Closed nealmcb closed 2 years ago

nealmcb commented 2 years ago

Thank you for this repo! But I'm getting a bit lost amongst the benchmarks and plethora of parameterizations.

Can you provide some examples of using the API provide here for a few common digital signature tasks, using the parameters that may be most likely to be standardized?

For extra credit, run thru the examples in a style similar to what Prof Bill Buchanan does at https://medium.com/asecuritysite-when-bob-met-alice/meet-the-standard-of-the-future-sphincs-ee2b9e4c7b5e. Or just show how to do his example if he's already using likely parameters.

bwesterb commented 2 years ago

This purpose of this repo is to be the reference implementation that goes along with the NIST submission. As such it will change, as the submission changes. I think the parameters will change a bit. The API used is standard for submissions to NIST PQC. Perhaps liboqs would be more suitable to your needs?

using the parameters that may be most likely to be standardized?

Could I turn that around: what parameters would you like for your application?

bwesterb commented 2 years ago

Closing due to inactivity.