diff options
author | Rich Salz <rsalz@openssl.org> | 2015-01-06 12:16:24 -0500 |
---|---|---|
committer | Rich Salz <rsalz@openssl.org> | 2015-01-06 12:16:24 -0500 |
commit | a09474dd2df89d5719b58bf6b3110344ea046ab9 (patch) | |
tree | e3492f58631d2244db43fecbf02c2329d27cd351 /doc/crypto/EVP_EncryptInit.pod | |
parent | 41cd41c4416f545a18ead37e09e437c75fa07c95 (diff) |
Some cleanup of L<> markup in pod files
Show only the #define, not the values, in BIO_f_buffer. Data
abstraction and we can remove a "see also" entry.
Remove internal forward reference to NOTES in EVP_EncryptInit; just
say "see below" as we do in the other pages.
Add missing (3) in pem.pod so the L<> entry is consistent.
Fix entry to point to the "master" page, not the symlink'd one.
Reviewed-by: Matt Caswell <matt@openssl.org>
Diffstat (limited to 'doc/crypto/EVP_EncryptInit.pod')
-rw-r--r-- | doc/crypto/EVP_EncryptInit.pod | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/crypto/EVP_EncryptInit.pod b/doc/crypto/EVP_EncryptInit.pod index d4b6af3bd1..6940de6ac4 100644 --- a/doc/crypto/EVP_EncryptInit.pod +++ b/doc/crypto/EVP_EncryptInit.pod @@ -133,7 +133,8 @@ room. The actual number of bytes written is placed in B<outl>. If padding is enabled (the default) then EVP_EncryptFinal_ex() encrypts the "final" data, that is any data that remains in a partial block. -It uses L<standard block padding|/NOTES> (aka PKCS padding). The encrypted +It uses standard block padding (aka PKCS padding) as described in +the NOTES section, below. The encrypted final data is written to B<out> which should have sufficient space for one cipher block. The number of bytes written is placed in B<outl>. After this function is called the encryption operation is finished and no further |