Daiki Ueno <[email protected]> writes: > I have a slight feeling that the current API is not easy to use, as the > caller needs to instantiate both hash and HMAC contexts, as there are no > correlations between the two:
On a more abstract level, are there any reasonable usecases for having one hash function for processing the message, and a different underlying hash function for the hmac used to produce the deterministic nonce? > What would you say to introducing a specialized API, something like the > following? > > void > ecdsa_sha256_sign_deterministic (const struct ecc_scalar *key, > size_t length, > const uint8_t *message, > struct dsa_signature *signature); I think that could sense, but we also need an advertised api function that takes the digest as input, for applications that want to process the message using multiple _update calls. Regards, /Niels -- Niels Möller. PGP key CB4962D070D77D7FCB8BA36271D8F1FF368C6677. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
