You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
One thing we could include as an option would be to automatically verify the signature after we generate it, as in:
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.
The text was updated successfully, but these errors were encountered: