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

Include optional signature verification after generation #11

Open
sfluhrer opened this issue Mar 27, 2021 · 0 comments
Open

Include optional signature verification after generation #11

sfluhrer opened this issue Mar 27, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@sfluhrer
Copy link
Collaborator

One thing we could include as an option would be to automatically verify the signature after we generate it, as in:

class sphincs_plus::key_shake256_128s_robust key;
// Do something to assign a private key
key.verify_after_sign(true);
auto signature = key.sign( "foo", 3 );
    // If this generated an invalid signature internally, this will throw an exception

This would save the application the trouble of doing it itself.

We'd test this by using the same trick as the fault detection attacks; we'd derive a class based on the real parameter set, but make the prf function get it wrong problematically.

@sfluhrer sfluhrer added the enhancement New feature or request label Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant