Attempt to (incompletely) document EVP_aes_*().

When EVP_des_cbc() was suggested, suggest EVP_aes_256_cbc() instead.

Remove mention of EVP_des_ede3_cbc() being the algorithm of choice for S/MIME.

Don't mention US-export limited RC2 algorithms, you'd better not know about
them.

1 files changed, 0 insertions, 7 deletions

diff --git a/src/lib/libcrypto/doc/PKCS7_encrypt.pod b/src/lib/libcrypto/doc/PKCS7_encrypt.pod
index e206684384..8bc77407b9 100644
--- a/src/lib/libcrypto/doc/PKCS7_encrypt.pod
+++ b/src/lib/libcrypto/doc/PKCS7_encrypt.pod
@@ -22,13 +22,6 @@ Only RSA keys are supported in PKCS#7 and envelopedData so the recipient
 certificates supplied to this function must all contain RSA public keys, though
 they do not have to be signed using the RSA algorithm.
 
-EVP_des_ede3_cbc() (triple DES) is the algorithm of choice for S/MIME use
-because most clients will support it.
-
-Some old "export grade" clients may only support weak encryption using 40 or 64
-bit RC2. These can be used by passing EVP_rc2_40_cbc() and EVP_rc2_64_cbc()
-respectively.
-
 The algorithm passed in the B<cipher> parameter must support ASN1 encoding of
 its parameters.