remove references to pycryptopp from docs

docs/debian.rst

@@ -43,7 +43,6 @@ dependencies as of the 1.9 release:
 
 * python
 * python-zfec
-* python-pycryptopp
 * python-foolscap
 * python-openssl (needed by foolscap)
 * python-twisted

docs/frontends/CLI.rst

@@ -44,7 +44,7 @@ arguments. "``tahoe --help``" might also provide something useful.
 Running "``tahoe --version``" will display a list of version strings, starting
 with the "allmydata" module (which contains the majority of the Tahoe-LAFS
 functionality) and including versions for a number of dependent libraries,
-like Twisted, Foolscap, pycryptopp, and zfec. "``tahoe --version-and-path``"
+like Twisted, Foolscap, and zfec. "``tahoe --version-and-path``"
 will also show the path from which each library was imported.
 
 On Unix systems, the shell expands filename wildcards (``'*'`` and ``'?'``)

docs/frontends/FTP-and-SFTP.rst

@@ -215,11 +215,6 @@ separately: debian puts it in the "python-twisted-conch" package. Conch
 requires the "pycrypto" package, which is a Python+C implementation of many
 cryptographic functions (the debian package is named "python-crypto").
 
-Note that "pycrypto" is different than the "pycryptopp" package that
-Tahoe-LAFS uses (which is a Python wrapper around the C++ -based Crypto++
-library, a library that is frequently installed as /usr/lib/libcryptopp.a, to
-avoid problems with non-alphanumerics in filenames).
-
 Immutable and Mutable Files
 ===========================
 

docs/historical/historical_known_issues.txt

@@ -272,22 +272,3 @@ that size, assume that they have been corrupted and are not retrievable from the
 Tahoe storage grid.  Tahoe v1.1 clients will refuse to upload files larger than
 12 GiB with a clean failure.  A future release of Tahoe will remove this
 limitation so that larger files can be uploaded.
-
-
-=== pycryptopp defect resulting in data corruption ===
-
-Versions of pycryptopp earlier than pycryptopp-0.5.0 had a defect
-which, when compiled with some compilers, would cause AES-256
-encryption and decryption to be computed incorrectly.  This could
-cause data corruption.  Tahoe v1.0 required, and came with a bundled
-copy of, pycryptopp v0.3.
-
-==== how to manage it ====
-
-You can detect whether pycryptopp-0.3 has this failure when it is
-compiled by your compiler.  Run the unit tests that come with
-pycryptopp-0.3: unpack the "pycryptopp-0.3.tar" file that comes in the
-Tahoe v1.0 {{{misc/dependencies}}} directory, cd into the resulting
-{{{pycryptopp-0.3.0}}} directory, and execute {{{python ./setup.py
-test}}}.  If the tests pass, then your compiler does not trigger this
-failure.

docs/windows.rst

@@ -78,7 +78,7 @@ Dependencies
 ------------
 
 Tahoe-LAFS depends upon several packages that use compiled C code, such as
-zfec, pycryptopp, and others. This code must be built separately for each
+zfec, and others. This code must be built separately for each
 platform (Windows, OS-X, and different flavors of Linux).
 
 Pre-compiled "wheels" of all Tahoe's dependencies are hosted on the