diff options
| author | Jung-uk Kim <jkim@FreeBSD.org> | 2014-08-07 16:49:55 +0000 |
|---|---|---|
| committer | Jung-uk Kim <jkim@FreeBSD.org> | 2014-08-07 16:49:55 +0000 |
| commit | cb6864802ed26a1031701a6a385961592a5cac25 (patch) | |
| tree | 785ec650cf5f2272f38035e18a3251735344f96d /doc/crypto/EVP_EncryptInit.pod | |
| parent | 2e22f5e2e00c1f1f599b03634ca27bb5b9ac471e (diff) | |
Notes
Diffstat (limited to 'doc/crypto/EVP_EncryptInit.pod')
| -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 1c4bf184a1b0..d11e054e48b3 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 |