diff options
author | Jeffrey Walton <noloader@gmail.com> | 2014-07-05 22:39:08 +0100 |
---|---|---|
committer | Janusz Kozerski <j.kozerski@samsung.com> | 2014-10-20 15:25:30 +0200 |
commit | ffc7b45a00a24b2144027f7722e4f71e94688bec (patch) | |
tree | 07b895b6a46e209cc6126149a03964610bed1d24 /doc | |
parent | 8537984de62969192a22fcc67ab610364d3e0e81 (diff) | |
download | openssl-ffc7b45a00a24b2144027f7722e4f71e94688bec.tar.gz openssl-ffc7b45a00a24b2144027f7722e4f71e94688bec.tar.bz2 openssl-ffc7b45a00a24b2144027f7722e4f71e94688bec.zip |
Added reference to platform specific cryptographic acceleration such as AES-NI
Diffstat (limited to 'doc')
-rw-r--r-- | doc/crypto/EVP_EncryptInit.pod | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/crypto/EVP_EncryptInit.pod b/doc/crypto/EVP_EncryptInit.pod index 1c4bf18..d11e054 100644 --- a/doc/crypto/EVP_EncryptInit.pod +++ b/doc/crypto/EVP_EncryptInit.pod @@ -344,7 +344,10 @@ bits and 12 rounds. 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 |