"Neal H. Walfield" <n...@walfield.org> writes: > So we could add: > > void sha1_collision_detection_init(...); > void sha1_collision_detection_update (struct sha1_ctx *ctx, size_t length, > const uint8_t *data) > error_code_t sha1_collision_detection_digest (struct sha1_ctx *ctx, size_t > length, uint8_t *digest) > > What do you think? Or, am I misunderstanding what you mean by > breaking compatibility?
I haven't yet read the background, so I don't know what I think about the feature in general. But from an api point of view, that looks reasonable. Do all three operations need new functions? Do you need an extended context struct too? Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
