| /freebsd-14.2/crypto/heimdal/lib/hx509/ |
| H A D | test_ca.in | 58 ${hxtool} issue-certificate \
106 ${hxtool} issue-certificate \
114 ${hxtool} issue-certificate \
123 ${hxtool} issue-certificate \
132 ${hxtool} issue-certificate \
141 ${hxtool} issue-certificate \
169 ${hxtool} issue-certificate \
189 ${hxtool} issue-certificate \
198 ${hxtool} issue-certificate \
206 ${hxtool} issue-certificate \
[all …]
|
| H A D | hxtool-commands.in | 39 long = "certificate"
132 long = "certificate"
182 long = "certificate"
212 long = "certificate"
318 argument="certificate ..."
335 name = "certificate-copy"
364 argument = "certificate"
550 long = "certificate"
597 long = "ca-certificate"
612 long = "certificate"
[all …]
|
| H A D | test_windows.in | 52 ${hxtool} issue-certificate \
58 --certificate="FILE:wca.pem" || exit 1
61 ${hxtool} issue-certificate \
67 --certificate="FILE:wdc.pem" \
70 --ca-certificate=FILE:wca.pem || exit 1
74 ${hxtool} issue-certificate \
81 --certificate="FILE:wuser.pem" \
82 --ca-certificate=FILE:wca.pem || exit 1
|
| H A D | test_cms.in | 56 --certificate=FILE:$srcdir/data/secp160r2TestClient.pem \
70 --certificate=FILE:$srcdir/data/test.crt,$srcdir/data/test.key \
84 --certificate=FILE:$srcdir/data/test.crt,$srcdir/data/test.key \
106 --certificate=FILE:$srcdir/data/test.crt,$srcdir/data/test.key \
141 --certificate=FILE:$srcdir/data/test.combined.crt \
216 --certificate=PKCS12:$srcdir/data/test.p12 \
249 --certificate=FILE:$srcdir/data/test.crt \
295 --certificate=FILE:$srcdir/data/sub-ca.crt \
458 --certificate=FILE:$srcdir/data/test.crt \
472 --certificate=FILE:$srcdir/data/test.crt \
[all …]
|
| /freebsd-14.2/crypto/openssl/doc/man3/ |
| H A D | X509_STORE_CTX_get_error.pod | 46 it is the certificate which signed the end entity certificate and so on.
55 certificate is relevant.
112 The issuer certificate of a locally looked up certificate could not be found.
193 The passed certificate is self-signed and the same certificate cannot be found
197 self-signed certificate in certificate chain>
206 The issuer certificate could not be found: this occurs if the issuer certificate
254 certificate.
261 the current certificate.
397 certificate chain.
450 the subject's certificate.
[all …]
|
| H A D | SSL_CTX_set_client_cert_cb.pod | 20 called when a client certificate is requested by a server and no certificate
29 set a certificate, a certificate/private key combination must be set
32 If no certificate should be set, "0" has to be returned and no certificate
42 During a handshake (or renegotiation) a server may request a certificate
46 When a certificate was set using the
57 If the callback function returns a certificate, the OpenSSL library
58 will try to load the private key and certificate data into the SSL
60 Thus it will permanently install the certificate and key for this SSL
63 a certificate.
79 certificate store for the SSL_CTX object (resulting in having to add
[all …]
|
| H A D | X509_check_ca.pod | 5 X509_check_ca - check if given certificate is CA certificate
15 This function checks if given certificate is CA certificate (can be used
16 to sign other certificates). The certificate must be a complete certificate
21 Function return 0, if it is not CA certificate, 1 if it is proper X509v3
22 CA certificate with B<basicConstraints> extension CA:TRUE,
23 3, if it is self-signed X509 v1 certificate, 4, if it is certificate with
26 extension telling that it is CA certificate.
30 Actually, any nonzero value means that this certificate could have been
|
| H A D | SSL_get_certificate.pod | 5 SSL_get_certificate, SSL_get_privatekey - retrieve TLS/SSL certificate and
18 certificate used as the local peer's identity.
21 RSA and ECDSA certificates. The certificate which is returned by
28 If it is called before certificate selection has occurred, it returns the most
29 recently added certificate, or NULL if no certificate has been added.
33 After certificate selection has occurred, it returns the certificate which was
34 selected during the handshake, or NULL if no certificate was selected (for
35 example, on a client where no client certificate is in use).
41 will depend on whether that callback is made before or after certificate
45 L<SSL_CTX_set_tlsext_status_cb(3)>. This callback occurs after certificate
[all …]
|
| H A D | SSL_CTX_use_certificate.pod | 16 - load certificate and key data
66 SSL_CTX_use_certificate() loads the certificate B<x> into B<ctx>,
68 certificates needed to form the complete certificate chain can be
84 SSL_CTX_use_certificate_chain_file() loads a certificate chain from
89 similar except it loads the certificate chain into B<ssl>.
96 to the certificate an error is returned. To change a [certificate/private-key]
103 certificate B<x>, private key B<key>, and certificate B<chain> onto the
142 key/certificate pairs at a time. The certificate used depends on the
147 one certificate or private key, consequently
155 certificate chain store for all certificate types, OpenSSL 1.0.2 and later
[all …]
|
| H A D | X509_get_extension_flags.pod | 15 X509_get_proxy_pathlen - retrieve certificate extension data
48 The certificate is an obsolete version 1 certificate.
52 The certificate contains a basic constraints extension.
60 The certificate is a valid proxy certificate.
73 The freshest CRL extension is present in the certificate.
77 The certificate contains an unhandled critical extension.
81 Some certificate extension values are invalid or inconsistent.
82 The certificate should be rejected.
95 inconsistent. The certificate should be rejected.
155 given certificate B<x> if it is a proxy certificate.
[all …]
|
| H A D | SSL_CTX_add1_chain_cert.pod | 11 chain certificate processing
42 associated with the current certificate of B<ctx> to B<sk>.
45 certificate B<x509> to the chain associated with the current certificate of
49 certificate of B<ctx>.
52 current certificate of B<ctx>. (This is implemented by calling
55 SSL_CTX_build_cert_chain() builds the certificate chain for B<ctx>.
71 (i.e. server or client) certificate. This is the last certificate loaded or
86 certificate after the current certificate. These two operations can be
91 this option sets that certificate to the current certificate and returns 1.
94 is not a server or a certificate has not been sent 0 is returned and
[all …]
|
| H A D | SSL_CTX_set_verify.pod | 12 - set various SSL/TLS parameters for peer certificate verification
57 server certificate verification step.
72 sent. A certificate callback will need to be set via
89 client, so the client will not send a certificate.
125 connection. Do not ask for a client certificate again during
165 The depth count is "level 0:peer certificate", "level 1: CA certificate",
171 a final trust anchor certificate.
178 for the certificate chain verification.
181 (the root CA certificate) and worked upward to the peer's certificate.
208 certificate or certificate callback to its configuration before it can
[all …]
|
| H A D | SSL_get_peer_certificate.pod | 7 SSL_get1_peer_certificate - get the X509 certificate of the peer
24 These functions return a pointer to the X509 certificate the
25 peer presented. If the peer did not present a certificate, NULL is returned.
30 certificate, if present. A client will only send a certificate when
35 That a certificate is returned does not indicate information about the
41 containing the peer certificate is freed. The X509 object must be explicitly
57 No certificate was presented by the peer or no connection was established.
59 =item Pointer to an X509 certificate
61 The return value points to the certificate presented by the peer.
|
| H A D | SSL_get_peer_cert_chain.pod | 5 SSL_get_peer_cert_chain, SSL_get0_verified_chain - get the X509 certificate
18 forming the certificate chain sent by the peer. If called on the client side,
19 the stack also contains the peer's certificate; if called on the server
20 side, the peer's certificate must be obtained separately using
22 If the peer did not present a certificate, NULL is returned.
28 SSL_get0_verified_chain() returns the B<verified> certificate chain
29 of the peer including the peer's end entity certificate. It must be called
40 The reference count of each certificate in the returned STACK_OF(X509) object
54 No certificate was presented by the peer or no connection was established
55 or the certificate chain is no longer available when a session is reused.
[all …]
|
| H A D | SSL_check_chain.pod | 5 SSL_check_chain - check certificate chain suitability
15 SSL_check_chain() checks whether certificate B<x>, private key B<pk> and
16 certificate chain B<chain> is suitable for use with the current session
25 If this flag is B<not> set then the certificate will never be used even
31 B<CERT_PKEY_EE_SIGNATURE>: the signature algorithm of the EE certificate is
37 B<CERT_PKEY_EE_PARAM>: the parameters of the end entity certificate are
42 B<CERT_PKEY_EXPLICIT_SIGN>: the end entity certificate algorithm
49 B<CERT_PKEY_CERT_TYPE>: the certificate type is acceptable. Only meaningful
57 clients after a certificate request message. It will typically be called
58 in the certificate callback.
[all …]
|
| H A D | OSSL_CMP_exec_certreq.pod | 55 OSSL_CMP_exec_IR_ses() requests an initial certificate from the given PKI.
57 OSSL_CMP_exec_CR_ses() requests an additional certificate.
61 OSSL_CMP_exec_KUR_ses() obtains an updated certificate.
63 These four types of certificate enrollment are implemented as macros
68 For IR, CR, and KUR, the certificate template to be used in the request
85 If the requested certificate is available the function returns 1 and the
87 If no error occurred but no certificate is available yet then
96 to see whether meanwhile the requested certificate is available.
101 OSSL_CMP_exec_RR_ses() requests the revocation of the certificate
126 trust, for instance via the caPubs field of a certificate response,
[all …]
|
| H A D | SSL_alert_type_string.pod | 40 non-fatal errors are certificate errors ("certificate expired",
99 =item "NC"/"no certificate"
101 A client, that was asked to send a certificate, does not send a certificate
104 =item "BC"/"bad certificate"
109 =item "UC"/"unsupported certificate"
113 =item "CR"/"certificate revoked"
115 A certificate was revoked by its signer.
117 =item "CE"/"certificate expired"
121 =item "CU"/"certificate unknown"
124 certificate, rendering it unacceptable.
[all …]
|
| /freebsd-14.2/crypto/openssl/doc/HOWTO/ |
| H A D | certificates.txt | 29 keys, so before you create a certificate or a certificate request, you
42 3. Creating a certificate request
44 To create a certificate, you need to start with a certificate request
45 (or, as some certificate authorities like to put it, "certificate
48 policies). A certificate request is sent to a certificate authority
49 to get it signed into a certificate. You can also sign the certificate
53 The certificate request is created like this:
73 4. Creating a self-signed test certificate
77 certificate for yourself. This is similar to creating a certificate
78 request, but creates a certificate instead of a certificate request.
[all …]
|
| /freebsd-14.2/crypto/openssl/doc/man1/ |
| H A D | openssl-x509.pod.in | 119 Generate a certificate from scratch, not using an input certificate
128 Output a PKCS#10 certificate request (rather than a certificate).
169 certificate request.
394 in the certificate.
403 to create a certificate even without providing an input certificate
419 When transforming a certificate to a new certificate
422 When transforming a certificate or certificate request,
525 A B<trusted certificate> is an ordinary certificate which has several
556 Sets the "alias" of the certificate. This will allow the certificate
718 Convert a certificate to a certificate request:
[all …]
|
| H A D | openssl-verification-options.pod | 61 uses of a target certificate the certificate may serve as a trust anchor.
79 A certificate, which may be CA certificate or an end-entity certificate,
104 First, a certificate chain is built up starting from the target certificate
118 A candidate issuer certificate matches a subject certificate
136 The certificate signature algorithm used to sign the subject certificate
369 public key strength when verifying certificate chains. For a certificate
429 construct a certificate chain from the target certificate to a trust anchor.
479 end-entity certificate nor the trust-anchor certificate count against the
519 end-entity certificate.
577 made on the uses of the certificate. A CA certificate B<must> have the
[all …]
|
| H A D | openssl-nseq.pod.in | 6 openssl-nseq - create or examine a Netscape certificate sequence
19 This command takes a file containing a Netscape certificate
21 file of certificates and converts it into a Netscape certificate
24 A Netscape certificate sequence is an old Netscape-specific format that
27 certificate enrollment. It was also used by Netscape certificate server.
48 Normally a Netscape certificate sequence will be input and the output
50 situation is reversed: a Netscape certificate sequence is created from
59 Output the certificates in a Netscape certificate sequence
63 Create a Netscape certificate sequence
|
| H A D | openssl-verify.pod.in | 6 openssl-verify - certificate verification command
24 [I<certificate> ...]
28 This command verifies certificate chains. If a certificate chain has multiple
51 Display information about the certificate chain that has been built (if
96 certificate files. This is useful if the first certificate filename begins
99 =item I<certificate> ...
102 given, this command will attempt to read a single certificate from standard
113 error 24 at 1 depth lookup:invalid CA certificate
117 and the depth. The depth is number of the certificate being verified when a
119 itself then 1 for the CA that signed the target certificate and so on.
[all …]
|
| /freebsd-14.2/crypto/openssl/doc/man7/ |
| H A D | x509.pod | 5 x509 - X.509 certificate handling
13 An X.509 certificate is a structured grouping of information about
15 (certificate revocation list) is a tool to help determine if a
16 certificate is still valid. The exact definition of those can be
18 In OpenSSL, the type X509 is used to express such a certificate, and
23 X509_REQ is used to express such a certificate request.
25 To handle some complex parts of a certificate, there are the types
27 a certificate attribute), X509_EXTENSION (to express a certificate
31 certificate and a corresponding private key.
40 functions handle PKCS#10 certificate requests.
[all …]
|
| /freebsd-14.2/crypto/heimdal/doc/ |
| H A D | hx509.texi | 309 certificate to services (by sending over the certificate and private
388 hxtool issue-certificate \
408 hxtool issue-certificate \
423 hxtool issue-certificate \
541 hxtool issue-certificate \
552 hxtool issue-certificate \
581 hx509 issue-certificate supports adding the email SAN to certificate by
587 hxtool issue-certificate \
598 hxtool issue-certificate \
621 hxtool issue-certificate \
[all …]
|
| /freebsd-14.2/crypto/openssh/ |
| H A D | PROTOCOL.certkeys | 1 This document describes a simple public-key certificate authentication
15 system already in SSH to allow certificate-based authentication. The
76 RSA certificate
94 DSA certificate
114 ECDSA certificate
134 ED25519 certificate
164 serial is an optional certificate serial number set by the CA to
184 certificate. Each represents a time in seconds since 1970-01-01
185 00:00:00. A certificate is considered valid if:
208 certificate. The valid key types for CA keys are ssh-rsa,
[all …]
|