Lines Matching +full:multi +full:- +full:word

1 .\" -*- mode: troff; coding: utf-8 -*-
58 .TH X509V3_CONFIG 5ossl 2025-09-30 3.5.4 OpenSSL
64 x509v3_config \- X509 V3 certificate extension configuration format
69 and CLI options such as \fB\-addext\fR.
90 type-value pairing where the type and value are separated by a colon.
95 \& multi\-valued
105 Multi-valued extensions have a short form and a long form. The short form
106 is a comma-separated list of names and values:
125 If an extension is multi-value and a field value must contain a comma the long
181 This is a multi-valued extension which indicates whether a certificate is
197 parameter set to \fBTRUE\fR. An end-user certificate must either have \fBCA:FALSE\fR
201 any sub-CA's, and can only sign end-entity certificates.
204 Key usage is a multi-valued extension consisting of a list of names of
225 \& \-\-\-\-\-                  \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
229 \& emailProtection        E\-mail Protection (S/MIME)
239 While IETF RFC 5280 says that \fBid-kp-serverAuth\fR and \fBid-kp-clientAuth\fR
259 The keyIdentifier is composed of the 160\-bit SHA\-1 hash of the value of the BIT
282 For self-signed certificates the AKID is suppressed unless \fBalways\fR is present.
285 for self-signed certificates and \fBkeyid\fR\f(CW\*(C`,\*(C'\fR \fBissuer\fR otherwise.
289 the issuer certificate is the same as the current one and it is not self-signed.
308 This is a multi-valued extension that supports several types of name
328 the distinguished name to use, as a set of name-value pairs.
329 Multi-valued AVAs can be formed by prefacing the name with a \fB+\fR character.
358 Non-ASCII Email Address conforming the syntax defined in Section 3.3 of RFC 6531
385 (although only a few values are well-known) and \fBlocation\fR has the same
403 This is a multi-valued extension whose values can be either a name-value
407 When a name-value pair is used, a DistributionPoint extension will
426 A multi-value field that contains the reasons for revocation. The recognized
459 This extension should only appear in CRLs. It is a multi-valued extension
472 A multi-value field that contains the reasons for revocation. The recognized
497 Multiple policies are comma-separated. For example:
556 This is a multi-valued extension which consisting of the names
576 This is a multi-valued extension. The name should
577 begin with the word \fBpermitted\fR or \fBexcluded\fR followed by a \fB;\fR. The rest of
603 This is a multi-valued extension consisting of a list of TLS extension
628 This is a multi-valued extensions which consists of a list of flags to be
644 The first way is to use the word ASN1 followed by the extension content
658 It is also possible to use the word DER to include the raw encoded data in any
684 \&\fBopenssl\-req\fR\|(1), \fBopenssl\-ca\fR\|(1), \fBopenssl\-x509\fR\|(1),
688 Copyright 2004\-2023 The OpenSSL Project Authors. All Rights Reserved.