diff options
Diffstat (limited to 'secure/lib/libcrypto/man/man3/ASN1_TYPE_get.3')
| -rw-r--r-- | secure/lib/libcrypto/man/man3/ASN1_TYPE_get.3 | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/secure/lib/libcrypto/man/man3/ASN1_TYPE_get.3 b/secure/lib/libcrypto/man/man3/ASN1_TYPE_get.3 index 99ed9567c134..f8882749da0f 100644 --- a/secure/lib/libcrypto/man/man3/ASN1_TYPE_get.3 +++ b/secure/lib/libcrypto/man/man3/ASN1_TYPE_get.3 @@ -1,4 +1,4 @@ -.\" Automatically generated by Pod::Man 4.11 (Pod::Simple 3.40) +.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.40) .\" .\" Standard preamble: .\" ======================================================================== @@ -133,7 +133,7 @@ .\" ======================================================================== .\" .IX Title "ASN1_TYPE_GET 3" -.TH ASN1_TYPE_GET 3 "2020-04-21" "1.1.1g" "OpenSSL" +.TH ASN1_TYPE_GET 3 "2020-09-22" "1.1.1h" "OpenSSL" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l @@ -169,7 +169,7 @@ up after the call. \&\fBASN1_TYPE_set1()\fR sets the value of \fBa\fR to \fBtype\fR a copy of \fBvalue\fR. .PP \&\fBASN1_TYPE_cmp()\fR compares \s-1ASN.1\s0 types \fBa\fR and \fBb\fR and returns 0 if -they are identical and non-zero otherwise. +they are identical and nonzero otherwise. .PP \&\fBASN1_TYPE_unpack_sequence()\fR attempts to parse the \s-1SEQUENCE\s0 present in \&\fBt\fR using the \s-1ASN.1\s0 structure \fBit\fR. If successful it returns a pointer @@ -197,12 +197,12 @@ length octets). .PP \&\fBASN1_TYPE_cmp()\fR may not return zero if two types are equivalent but have different encodings. For example the single content octet of the boolean \s-1TRUE\s0 -value under \s-1BER\s0 can have any non-zero encoding but \fBASN1_TYPE_cmp()\fR will +value under \s-1BER\s0 can have any nonzero encoding but \fBASN1_TYPE_cmp()\fR will only return zero if the values are the same. .PP If either or both of the parameters passed to \fBASN1_TYPE_cmp()\fR is \s-1NULL\s0 the -return value is non-zero. Technically if both parameters are \s-1NULL\s0 the two -types could be absent \s-1OPTIONAL\s0 fields and so should match, however passing +return value is nonzero. Technically if both parameters are \s-1NULL\s0 the two +types could be absent \s-1OPTIONAL\s0 fields and so should match, however, passing \&\s-1NULL\s0 values could also indicate a programming error (for example an unparsable type which returns \s-1NULL\s0) for types which do \fBnot\fR match. So applications should handle the case of two absent values separately. @@ -214,7 +214,7 @@ applications should handle the case of two absent values separately. .PP \&\fBASN1_TYPE_set1()\fR returns 1 for success and 0 for failure. .PP -\&\fBASN1_TYPE_cmp()\fR returns 0 if the types are identical and non-zero otherwise. +\&\fBASN1_TYPE_cmp()\fR returns 0 if the types are identical and nonzero otherwise. .PP \&\fBASN1_TYPE_unpack_sequence()\fR returns a pointer to an \s-1ASN.1\s0 structure or \&\s-1NULL\s0 on failure. |