From: Jeffrey Walton <noloader@gmail.com>
Date: Sat, 5 Jul 2014 21:39:08 +0000 (+0100)
Subject: Added reference to platform specific cryptographic acceleration such as AES-NI
X-Git-Tag: master-pre-reformat~549
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=75b7606881b08a892f487629cc30e63dff1800cb;p=thirdparty%2Fopenssl.git

Added reference to platform specific cryptographic acceleration such as AES-NI
---

diff --git a/doc/crypto/EVP_EncryptInit.pod b/doc/crypto/EVP_EncryptInit.pod
index 3b132c4490c..e4404637561 100644
--- a/doc/crypto/EVP_EncryptInit.pod
+++ b/doc/crypto/EVP_EncryptInit.pod
@@ -434,7 +434,10 @@ for AES.
 
 Where possible the B<EVP> interface to symmetric ciphers should be used in
 preference to the low level interfaces. This is because the code then becomes
-transparent to the cipher used and much more flexible.
+transparent to the cipher used and much more flexible. Additionally, the
+B<EVP> interface will ensure the use of platform specific cryptographic
+acceleration such as AES-NI (the low level interfaces do not provide the
+guarantee).
 
 PKCS padding works by adding B<n> padding bytes of value B<n> to make the total 
 length of the encrypted data a multiple of the block size. Padding is always