diff options
author | schwarze <> | 2021-11-26 13:35:10 +0000 |
---|---|---|
committer | schwarze <> | 2021-11-26 13:35:10 +0000 |
commit | 4e43bd6737c855a4f156cb8361e1ba49a89f6ca7 (patch) | |
tree | 594c2463a8c90579965437b61891448c447fcc1e /src | |
parent | d32ec31a7cdba9039a7bc50e7a4add51f70b429e (diff) | |
download | openbsd-4e43bd6737c855a4f156cb8361e1ba49a89f6ca7.tar.gz openbsd-4e43bd6737c855a4f156cb8361e1ba49a89f6ca7.tar.bz2 openbsd-4e43bd6737c855a4f156cb8361e1ba49a89f6ca7.zip |
after the bugfix in x509_vfy.c rev. 1.100,
replace the BUGS section with a shorter CAVEATS section
Diffstat (limited to 'src')
-rw-r--r-- | src/lib/libcrypto/man/X509_get_pubkey_parameters.3 | 28 |
1 files changed, 12 insertions, 16 deletions
diff --git a/src/lib/libcrypto/man/X509_get_pubkey_parameters.3 b/src/lib/libcrypto/man/X509_get_pubkey_parameters.3 index 7cb163e751..181361477e 100644 --- a/src/lib/libcrypto/man/X509_get_pubkey_parameters.3 +++ b/src/lib/libcrypto/man/X509_get_pubkey_parameters.3 | |||
@@ -1,4 +1,4 @@ | |||
1 | .\" $OpenBSD: X509_get_pubkey_parameters.3,v 1.1 2021/10/19 17:42:49 schwarze Exp $ | 1 | .\" $OpenBSD: X509_get_pubkey_parameters.3,v 1.2 2021/11/26 13:35:10 schwarze Exp $ |
2 | .\" | 2 | .\" |
3 | .\" Copyright (c) 2021 Ingo Schwarze <schwarze@openbsd.org> | 3 | .\" Copyright (c) 2021 Ingo Schwarze <schwarze@openbsd.org> |
4 | .\" | 4 | .\" |
@@ -14,7 +14,7 @@ | |||
14 | .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF | 14 | .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF |
15 | .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. | 15 | .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. |
16 | .\" | 16 | .\" |
17 | .Dd $Mdocdate: October 19 2021 $ | 17 | .Dd $Mdocdate: November 26 2021 $ |
18 | .Dt X509_GET_PUBKEY_PARAMETERS 3 | 18 | .Dt X509_GET_PUBKEY_PARAMETERS 3 |
19 | .Os | 19 | .Os |
20 | .Sh NAME | 20 | .Sh NAME |
@@ -86,18 +86,14 @@ contain complete public key parameters. | |||
86 | .Fn X509_get_pubkey_parameters | 86 | .Fn X509_get_pubkey_parameters |
87 | first appeared in SSLeay 0.8.0 and has been available since | 87 | first appeared in SSLeay 0.8.0 and has been available since |
88 | .Ox 2.4 . | 88 | .Ox 2.4 . |
89 | .Sh BUGS | 89 | .Sh CAVEATS |
90 | If an error occurs while copying parameters with | 90 | If |
91 | .Xr EVP_PKEY_copy_parameters 3 , | ||
92 | .Fn X509_get_pubkey_parameters | ||
93 | indicates success regardless. | ||
94 | In this case, it is possible that a part of the parameters was copied | ||
95 | while another part remained in its former state, or that nothing got | ||
96 | copied at all. | ||
97 | .Pp | ||
98 | Some errors of this kind, for example some kinds of key type | ||
99 | mismatches and some kinds of memory allocation failures, can be | ||
100 | detected by inspecting the error stack after | ||
101 | .Fn X509_get_pubkey_parameters | 91 | .Fn X509_get_pubkey_parameters |
102 | returns successfully, but some other kinds of algorithm-specific | 92 | fails and returns 0, a part of the parameters may or may not have |
103 | copying failures might be impossible to detect at all. | 93 | been copied before the failure was detected, whereas other parts of |
94 | .Fa pkey | ||
95 | and | ||
96 | .Fa chain | ||
97 | may remain unchanged. | ||
98 | So in case of failure, the state of the arguments may change | ||
99 | and possibly become inconsistent. | ||