Added notes to clarify that binascii.crc32(), zlib.crc32(), and
zlib.adler32() are not suitable as general hash functions.
diff --git a/Doc/lib/libbinascii.tex b/Doc/lib/libbinascii.tex
index 0ce0996..12c135e 100644
--- a/Doc/lib/libbinascii.tex
+++ b/Doc/lib/libbinascii.tex
@@ -92,7 +92,9 @@
\begin{funcdesc}{crc32}{data\optional{, crc}}
Compute CRC-32, the 32-bit checksum of data, starting with an initial
-crc. This is consistent with the ZIP file checksum. Use as follows:
+crc. This is consistent with the ZIP file checksum. Since the
+algorithm is designed for use as a checksum algorithm, it is not
+suitable for use as a general hash algorithm. Use as follows:
\begin{verbatim}
print binascii.crc32("hello world")
# Or, in two pieces:
diff --git a/Doc/lib/libzlib.tex b/Doc/lib/libzlib.tex
index c78523b..e384b1f 100644
--- a/Doc/lib/libzlib.tex
+++ b/Doc/lib/libzlib.tex
@@ -29,7 +29,9 @@
used. This allows computing a running checksum over the
concatenation of several input strings. The algorithm is not
cryptographically strong, and should not be used for
- authentication or digital signatures.
+ authentication or digital signatures. Since the algorithm is
+ designed for use as a checksum algorithm, it is not suitable for
+ use as a general hash algorithm.
\end{funcdesc}
\begin{funcdesc}{compress}{string\optional{, level}}
@@ -58,7 +60,9 @@
checksum; otherwise, a fixed default value is used. This allows
computing a running checksum over the concatenation of several
input strings. The algorithm is not cryptographically strong, and
- should not be used for authentication or digital signatures.
+ should not be used for authentication or digital signatures. Since
+ the algorithm is designed for use as a checksum algorithm, it is not
+ suitable for use as a general hash algorithm.
\end{funcdesc}
\begin{funcdesc}{decompress}{string\optional{, wbits\optional{, bufsize}}}