aboutsummaryrefslogtreecommitdiff
path: root/openssl/doc/crypto/EVP_EncryptInit.pod
diff options
context:
space:
mode:
authorMike DePaulo <mikedep333@gmail.com>2015-01-10 12:26:41 -0500
committerMike DePaulo <mikedep333@gmail.com>2015-02-28 07:16:26 -0500
commit29d3851ef58419274f5f80a050d22b14319eff74 (patch)
treec70cbddb9c2100abb5e0e5fdd5acaf180b89b946 /openssl/doc/crypto/EVP_EncryptInit.pod
parenta1babdda61e8cb3f8d0608d87120ba46ca91a21d (diff)
downloadvcxsrv-29d3851ef58419274f5f80a050d22b14319eff74.tar.gz
vcxsrv-29d3851ef58419274f5f80a050d22b14319eff74.tar.bz2
vcxsrv-29d3851ef58419274f5f80a050d22b14319eff74.zip
Update openssl to version openssl-1.0.1k
Diffstat (limited to 'openssl/doc/crypto/EVP_EncryptInit.pod')
-rw-r--r--openssl/doc/crypto/EVP_EncryptInit.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/openssl/doc/crypto/EVP_EncryptInit.pod b/openssl/doc/crypto/EVP_EncryptInit.pod
index 4e22edcd6..ed027b387 100644
--- a/openssl/doc/crypto/EVP_EncryptInit.pod
+++ b/openssl/doc/crypto/EVP_EncryptInit.pod
@@ -115,7 +115,7 @@ writes the encrypted version to B<out>. This function can be called
multiple times to encrypt successive blocks of data. The amount
of data written depends on the block alignment of the encrypted data:
as a result the amount of data written may be anything from zero bytes
-to (inl + cipher_block_size - 1) so B<outl> should contain sufficient
+to (inl + cipher_block_size - 1) so B<out> should contain sufficient
room. The actual number of bytes written is placed in B<outl>.
If padding is enabled (the default) then EVP_EncryptFinal_ex() encrypts