generic-library/openssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix some minor documentation issues

Browse Source 
Reviewed-by: Emilia Käsper <emilia@openssl.org>
This commit is contained in:
Matt Caswell 2015-02-20 09:18:29 +00:00
parent eafdbd8ec3
commit 1aff39de76
2 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/crypto/d2i_ECPrivateKey.pod
View File

@ -31,8 +31,8 @@ for a description of point_conversion_form.
When reading a private key encoded without an associated public key (e.g. if When reading a private key encoded without an associated public key (e.g. if
EC_PKEY_NO_PUBKEY has been used - see below), then d2i_ECPrivateKey generates EC_PKEY_NO_PUBKEY has been used - see below), then d2i_ECPrivateKey generates
the missing public key automatically. Private keys encoded without parameters the missing public key automatically. Private keys encoded without parameters
(e.g. if EC_PKEY_NO_PARAMETERS has been used - see below) then the key cannot be (e.g. if EC_PKEY_NO_PARAMETERS has been used - see below) cannot be loaded using
loaded using d2i_ECPrivateKey. d2i_ECPrivateKey.
The functions EC_KEY_get_enc_flags and EC_KEY_set_enc_flags get and set the The functions EC_KEY_get_enc_flags and EC_KEY_set_enc_flags get and set the
value of the encoding flags for the B<key>. There are two encoding flags value of the encoding flags for the B<key>. There are two encoding flags

6
doc/crypto/d2i_X509.pod
View File

@ -82,8 +82,7 @@ can trap the unwary. See the B<WARNINGS> section for some common
errors. errors.
The reason for the auto increment behaviour is to reflect a typical The reason for the auto increment behaviour is to reflect a typical
usage of ASN1 functions: after one structure is encoded or decoded if (a != NULL) usage of ASN1 functions: after one structure is encoded or decoded
(*a) = ret;
another will processed after it. another will processed after it.
=head1 EXAMPLES =head1 EXAMPLES
@ -205,8 +204,7 @@ of this "reuse" behaviour is strongly discouraged.
i2d_X509() will not return an error in many versions of OpenSSL, i2d_X509() will not return an error in many versions of OpenSSL,
if mandatory fields are not initialized due to a programming error if mandatory fields are not initialized due to a programming error
then the encoded structure may contain invalid data or omit the if (a != NULL) then the encoded structure may contain invalid data or omit the
(*a) = ret;
fields entirely and will not be parsed by d2i_X509(). This may be fields entirely and will not be parsed by d2i_X509(). This may be
fixed in future so code should not assume that i2d_X509() will fixed in future so code should not assume that i2d_X509() will
always succeed. always succeed.