From 648a9f7c2fce2960723cd330fd9565a59ff3927b Mon Sep 17 00:00:00 2001 From: Jeffrey Walton Date: Sat, 5 Jul 2014 22:39:08 +0100 Subject: [PATCH] Added reference to platform specific cryptographic acceleration such as AES-NI --- doc/crypto/EVP_EncryptInit.pod | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/crypto/EVP_EncryptInit.pod b/doc/crypto/EVP_EncryptInit.pod index f6e4396ade..8d7636c788 100644 --- a/doc/crypto/EVP_EncryptInit.pod +++ b/doc/crypto/EVP_EncryptInit.pod @@ -433,7 +433,10 @@ for AES. Where possible the B 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 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 padding bytes of value B to make the total length of the encrypted data a multiple of the block size. Padding is always -- 2.34.1