Revision aa3b4b4d deps/openssl/openssl/doc/crypto/EVP_EncryptInit.pod
deps/openssl/openssl/doc/crypto/EVP_EncryptInit.pod | ||
---|---|---|
344 | 344 |
|
345 | 345 |
Where possible the B<EVP> interface to symmetric ciphers should be used in |
346 | 346 |
preference to the low level interfaces. This is because the code then becomes |
347 |
transparent to the cipher used and much more flexible. |
|
347 |
transparent to the cipher used and much more flexible. Additionally, the |
|
348 |
B<EVP> interface will ensure the use of platform specific cryptographic |
|
349 |
acceleration such as AES-NI (the low level interfaces do not provide the |
|
350 |
guarantee). |
|
348 | 351 |
|
349 | 352 |
PKCS padding works by adding B<n> padding bytes of value B<n> to make the total |
350 | 353 |
length of the encrypted data a multiple of the block size. Padding is always |
Also available in: Unified diff