AuroraMiddleware/libtomcrypt
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

add missing hash descriptors to the documentation. sha1 no longer recommended.

Browse Source
This commit is contained in:
Kelvin Sherlock 2017-04-23 15:34:49 -04:00 committed by Steffen Jaeckel
parent 8e03799eb6
commit b234e6b4ca
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
crypt.tex
View File

@ -2167,21 +2167,33 @@ The following hashes are provided as of this release within the LibTomCrypt libr
\begin{tabular}{|c|c|c|}
\hline \textbf{Name} & \textbf{Descriptor Name} & \textbf{Size of Message Digest (bytes)} \\
\hline WHIRLPOOL & whirlpool\_desc & 64 \\
\hline SHA3-512 & sha3\_512\_desc & 64 \\
\hline SHA-512 & sha512\_desc & 64 \\
\hline BLAKE2B-512 & blake2b\_512\_desc & 64 \\
\hline SHA3-384 & sha3\_384\_desc & 48 \\
\hline SHA-384 & sha384\_desc & 48 \\
\hline RIPEMD-320 & rmd160\_desc & 40 \\
\hline SHA-512/256 & sha512\_256\_desc & 32 \\
\hline SHA3-256 & sha3\_256\_desc & 32 \\
\hline SHA-256 & sha256\_desc & 32 \\
\hline RIPEMD-256 & rmd160\_desc & 32 \\
\hline BLAKE2S-256 & blake2s\_256\_desc & 32 \\
\hline BLAKE2B-256 & blake2b\_256\_desc & 32 \\
\hline SHA-512/224 & sha512\_224\_desc & 28 \\
\hline SHA3-224 & sha3\_224\_desc & 28 \\
\hline SHA-224 & sha224\_desc & 28 \\
\hline BLAKE2S-224 & blake2s\_224\_desc & 28 \\
\hline BLAKE2B-384 & blake2b\_384\_desc & 48 \\
\hline TIGER-192 & tiger\_desc & 24 \\
\hline SHA-1 & sha1\_desc & 20 \\
\hline RIPEMD-160 & rmd160\_desc & 20 \\
\hline BLAKE2S-160 & blake2s\_160\_desc & 20 \\
\hline BLAKE2B-160 & blake2b\_160\_desc & 20 \\
\hline RIPEMD-128 & rmd128\_desc & 16 \\
\hline MD5 & md5\_desc & 16 \\
\hline MD4 & md4\_desc & 16 \\
\hline MD2 & md2\_desc & 16 \\
\hline BLAKE2S-128 & blake2s\_128\_desc & 16 \\
\hline
\end{tabular}
\end{center}
@ -2245,7 +2257,7 @@ int main(void)
\mysection{Notice}
It is highly recommended that you \textbf{not} use the MD4 or MD5 hashes for the purposes of digital signatures or authentication codes.
It is highly recommended that you \textbf{not} use the MD2, MD4, MD5, or SHA-1 hashes for the purposes of digital signatures or authentication codes.
These hashes are provided for completeness and they still can be used for the purposes of password hashing or one-way accumulators
(e.g. Yarrow).