Lines Matching +full:multi +full:- +full:address
5 x509v3_config - X509 V3 certificate extension configuration format
11 and CLI options such as B<-addext>.
30 type-value pairing where the type and value are separated by a colon.
34 multi-valued
43 Multi-valued extensions have a short form and a long form. The short form
44 is a comma-separated list of names and values:
59 If an extension is multi-value and a field value must contain a comma the long
109 This is a multi-valued extension which indicates whether a certificate is
123 parameter set to B<TRUE>. An end-user certificate must either have B<CA:FALSE>
127 any sub-CA's, and can only sign end-entity certificates.
131 Key usage is a multi-valued extension consisting of a list of names of
150 ----- ----------------------------------
154 emailProtection E-mail Protection (S/MIME)
163 While IETF RFC 5280 says that B<id-kp-serverAuth> and B<id-kp-clientAuth>
179 The keyIdentifier is composed of the 160-bit SHA-1 hash of the value of the BIT
197 For self-signed certificates the AKID is suppressed unless B<always> is present.
199 "none" was given for self-signed certificates and "keyid, issuer" otherwise.
203 the issuer certificate is the same as the current one and it is not self-signed.
220 This is a multi-valued extension that supports several types of name
222 B<email> (an email address),
226 B<IP> (an IP address),
237 The IP address used in the B<IP> option can be in either IPv4 or IPv6 format.
240 the distinguished name to use, as a set of name-value pairs.
241 Multi-valued AVAs can be formed by prefacing the name with a B<+> character.
268 Non-ASCII Email Address conforming the syntax defined in Section 3.3 of RFC 6531
270 address should be provided as UTF8String. To enforce the valid representation in
293 (although only a few values are well-known) and B<location> has the same
310 This is a multi-valued extension whose values can be either a name-value
314 When a name-value pair is used, a DistributionPoint extension will
339 A multi-value field that contains the reasons for revocation. The recognized
371 This extension should only appear in CRLs. It is a multi-valued extension
389 A multi-value field that contains the reasons for revocation. The recognized
416 Multiple policies are comma-separated. For example:
466 This is a multi-valued extension which consisting of the names
484 This is a multi-valued extension. The name should
509 This is a multi-valued extension consisting of a list of TLS extension
535 This is a multi-valued extensions which consists of a list of flags to be
588 L<openssl-req(1)>, L<openssl-ca(1)>, L<openssl-x509(1)>,
593 Copyright 2004-2023 The OpenSSL Project Authors. All Rights Reserved.