diff options
| author | Jeffrey Walton <noloader@gmail.com> | 2014-07-05 22:39:08 +0100 |
|---|---|---|
| committer | Matt Caswell <matt@openssl.org> | 2014-07-06 00:04:32 +0100 |
| commit | 157fd05aad0ac7b1f50c89e4a9373f9a561574d9 (patch) | |
| tree | b9fa6f7d71a784f85cbadaa39ddd9a3e395df0ac /doc | |
| parent | 9f510ceb5d3a15c8e155f9d34609bd9b15a32aba (diff) | |
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 1c4bf184a1..d11e054e48 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 |