Le Thu, Jun 09, 2022 at 06:47:12PM +0200, Niels Möller a écrit :
> Corentin Labbe <[email protected]> writes:
>
> > COMPRESS macro and sha256_compress/sha512_compress do the same thing,
> > so replace COMPRESS by the later.
>
> This second patch generates lots of pointer type warnings, so I've done
> it slightly differently. Pushed your first patch and followup changes to
> a branch export-sha256_compress.
>
> Documentation for all of the compress functions is needed (both new
> once, and md5_compress and sha1_compress which were previously
> considered internal). Can you help with that? They need a short
> paragraph each in nettle.texinfo, in the same reference section as the
> corresponding hash function. The most important detail is to be clear
> about the representation and size of the state argument.
>
> Regards,
> /Niels
>
Hello
Does this is what you want ?
--- a/nettle.texinfo
+++ b/nettle.texinfo
@@ -929,6 +929,13 @@ This function also resets the context in the same way as
@code{md5_init}.
@end deftypefun
+@deftypefun void md5_compress (uint32_t *@var{state}, uint8_t *@var{input})
+Perform a raw MD5 compress on MD5_BLOCK_SIZE bytes from @var{input} using
@var{state} as IV (which should be at
+least MD5_BLOCK_SIZE long). The output is stored in @var{state}.
+This function is usefull only if you need to use different IV from standard MD5
+or want to do MD5 at hand.
+@end deftypefun
+
The normal way to use MD5 is to call the functions in order: First
@code{md5_init}, then @code{md5_update} zero or more times, and finally
@code{md5_digest}. After @code{md5_digest}, the context is reset to
Regards
_______________________________________________
nettle-bugs mailing list -- [email protected]
To unsubscribe send an email to [email protected]
