diff options
author | jmc <> | 2016-12-03 13:36:03 +0000 |
---|---|---|
committer | jmc <> | 2016-12-03 13:36:03 +0000 |
commit | 767bff4409ce6a123bd88bf933cd119b0224b542 (patch) | |
tree | a73acb78b90989de6c4e159825f7290f7f3e87b0 /src/lib/libcrypto/man/X509_STORE_CTX_get_error.3 | |
parent | 23857f34c1e1f6362c4594df7a9ebaaaad450986 (diff) | |
download | openbsd-767bff4409ce6a123bd88bf933cd119b0224b542.tar.gz openbsd-767bff4409ce6a123bd88bf933cd119b0224b542.tar.bz2 openbsd-767bff4409ce6a123bd88bf933cd119b0224b542.zip |
various cleanup;
Diffstat (limited to 'src/lib/libcrypto/man/X509_STORE_CTX_get_error.3')
-rw-r--r-- | src/lib/libcrypto/man/X509_STORE_CTX_get_error.3 | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/src/lib/libcrypto/man/X509_STORE_CTX_get_error.3 b/src/lib/libcrypto/man/X509_STORE_CTX_get_error.3 index 85b7ac06f0..36f153af5a 100644 --- a/src/lib/libcrypto/man/X509_STORE_CTX_get_error.3 +++ b/src/lib/libcrypto/man/X509_STORE_CTX_get_error.3 | |||
@@ -1,6 +1,6 @@ | |||
1 | .\" $OpenBSD: X509_STORE_CTX_get_error.3,v 1.2 2016/11/06 15:52:50 jmc Exp $ | 1 | .\" $OpenBSD: X509_STORE_CTX_get_error.3,v 1.3 2016/12/03 13:36:03 jmc Exp $ |
2 | .\" | 2 | .\" |
3 | .Dd $Mdocdate: November 6 2016 $ | 3 | .Dd $Mdocdate: December 3 2016 $ |
4 | .Dt X509_STORE_CTX_GET_ERROR 3 | 4 | .Dt X509_STORE_CTX_GET_ERROR 3 |
5 | .Os | 5 | .Os |
6 | .Sh NAME | 6 | .Sh NAME |
@@ -86,7 +86,7 @@ successful, the returned chain may be incomplete or invalid. | |||
86 | The returned chain persists after the | 86 | The returned chain persists after the |
87 | .Fa ctx | 87 | .Fa ctx |
88 | structure is freed. | 88 | structure is freed. |
89 | When it is no longer needed, it should be free up using | 89 | When it is no longer needed, it should be freed up using |
90 | .Fn sk_X509_pop_free chain X509_free . | 90 | .Fn sk_X509_pop_free chain X509_free . |
91 | .Pp | 91 | .Pp |
92 | .Fn X509_verify_cert_error_string | 92 | .Fn X509_verify_cert_error_string |
@@ -144,8 +144,8 @@ The CRL of a certificate could not be found. | |||
144 | No unable to decrypt certificate's signature | 144 | No unable to decrypt certificate's signature |
145 | The certificate signature could not be decrypted. | 145 | The certificate signature could not be decrypted. |
146 | This means that the actual signature value could not be determined | 146 | This means that the actual signature value could not be determined |
147 | rather than it not matching the expected value, this is only meaningful | 147 | rather than it not matching the expected value. |
148 | for RSA keys. | 148 | This is only meaningful for RSA keys. |
149 | .It Dv X509_V_ERR_UNABLE_TO_DECRYPT_CRL_SIGNATURE : \ | 149 | .It Dv X509_V_ERR_UNABLE_TO_DECRYPT_CRL_SIGNATURE : \ |
150 | No unable to decrypt CRL's signature | 150 | No unable to decrypt CRL's signature |
151 | The CRL signature could not be decrypted: this means that the actual | 151 | The CRL signature could not be decrypted: this means that the actual |
@@ -219,7 +219,7 @@ The root CA is marked to reject the specified purpose. | |||
219 | .It Dv X509_V_ERR_SUBJECT_ISSUER_MISMATCH : No subject issuer mismatch | 219 | .It Dv X509_V_ERR_SUBJECT_ISSUER_MISMATCH : No subject issuer mismatch |
220 | The current candidate issuer certificate was rejected because its | 220 | The current candidate issuer certificate was rejected because its |
221 | subject name did not match the issuer name of the current certificate. | 221 | subject name did not match the issuer name of the current certificate. |
222 | This is only set if issuer check debugging is enabled it is used for | 222 | This is only set if issuer check debugging is enabled; it is used for |
223 | status notification and is | 223 | status notification and is |
224 | .Sy not | 224 | .Sy not |
225 | in itself an error. | 225 | in itself an error. |
@@ -228,7 +228,7 @@ in itself an error. | |||
228 | The current candidate issuer certificate was rejected because its | 228 | The current candidate issuer certificate was rejected because its |
229 | subject key identifier was present and did not match the authority key | 229 | subject key identifier was present and did not match the authority key |
230 | identifier current certificate. | 230 | identifier current certificate. |
231 | This is only set if issuer check debugging is enabled it is used for | 231 | This is only set if issuer check debugging is enabled; it is used for |
232 | status notification and is | 232 | status notification and is |
233 | .Sy not | 233 | .Sy not |
234 | in itself an error. | 234 | in itself an error. |
@@ -237,7 +237,7 @@ in itself an error. | |||
237 | The current candidate issuer certificate was rejected because its issuer | 237 | The current candidate issuer certificate was rejected because its issuer |
238 | name and serial number was present and did not match the authority key | 238 | name and serial number was present and did not match the authority key |
239 | identifier of the current certificate. | 239 | identifier of the current certificate. |
240 | This is only set if issuer check debugging is enabled it is used for | 240 | This is only set if issuer check debugging is enabled; it is used for |
241 | status notification and is | 241 | status notification and is |
242 | .Sy not | 242 | .Sy not |
243 | in itself an error. | 243 | in itself an error. |
@@ -259,7 +259,7 @@ A certificate policies extension had an invalid value (for example an | |||
259 | incorrect encoding) or some value inconsistent with other extensions. | 259 | incorrect encoding) or some value inconsistent with other extensions. |
260 | This error only occurs if policy processing is enabled. | 260 | This error only occurs if policy processing is enabled. |
261 | .It Dv X509_V_ERR_NO_EXPLICIT_POLICY : No no explicit policy | 261 | .It Dv X509_V_ERR_NO_EXPLICIT_POLICY : No no explicit policy |
262 | The verification flags were set to require and explicit policy but none | 262 | The verification flags were set to require an explicit policy but none |
263 | was present. | 263 | was present. |
264 | .It Dv X509_V_ERR_DIFFERENT_CRL_SCOPE : No different CRL scope | 264 | .It Dv X509_V_ERR_DIFFERENT_CRL_SCOPE : No different CRL scope |
265 | The only CRLs that could be found did not match the scope of the | 265 | The only CRLs that could be found did not match the scope of the |
@@ -284,7 +284,7 @@ types. | |||
284 | .It Dv X509_V_ERR_UNSUPPORTED_CONSTRAINT_SYNTAX : \ | 284 | .It Dv X509_V_ERR_UNSUPPORTED_CONSTRAINT_SYNTAX : \ |
285 | No unsupported or invalid name constraint syntax | 285 | No unsupported or invalid name constraint syntax |
286 | The format of the name constraint is not recognised: for example an | 286 | The format of the name constraint is not recognised: for example an |
287 | email address format of a form not mentioned in RFC3280. | 287 | email address format of a form not mentioned in RFC 3280. |
288 | This could be caused by a garbage extension or some new feature not | 288 | This could be caused by a garbage extension or some new feature not |
289 | currently supported. | 289 | currently supported. |
290 | .It Dv X509_V_ERR_CRL_PATH_VALIDATION_ERROR : No CRL path validation error | 290 | .It Dv X509_V_ERR_CRL_PATH_VALIDATION_ERROR : No CRL path validation error |