Lines Matching full:extensions

67 Several OpenSSL commands can add extensions to a certificate or
75 This page uses \fBextensions\fR as the name of the section, when needed
102 String extensions simply have a string which contains either the value itself
105 Multi-valued extensions have a short form and a long form. The short form
115 \& [extensions]
136 \& [extensions]
149 \& [extensions]
161 \& [extensions]
169 The syntax of raw extensions is defined by the source code that parses
174 must be used, see the "ARBITRARY EXTENSIONS" section for more details.
175 .SH "STANDARD EXTENSIONS"
176 .IX Header "STANDARD EXTENSIONS"
348 \& [extensions]
444 \& [extensions]
483 \& [extensions]
532 \& [extensions]
615 .SH "DEPRECATED EXTENSIONS"
616 .IX Header "DEPRECATED EXTENSIONS"
617 The following extensions are non standard, Netscape specific and largely
619 .SS "Netscape String extensions"
620 .IX Subsection "Netscape String extensions"
623 Other extensions of this type are: \fBnsBaseUrl\fR,
628 This is a multi-valued extensions which consists of a list of flags to be
630 be used. The basicConstraints, keyUsage and extended key usage extensions are
635 .SH "ARBITRARY EXTENSIONS"
636 .IX Header "ARBITRARY EXTENSIONS"
639 format for supported extensions. Extreme care should be taken to ensure that
642 There are two ways to encode arbitrary extensions.
649 \& [extensions]
677 purposes prohibited by their extensions because a specific application does
678 not recognize or honour the values of the relevant extensions.
681 invalid extensions if they are not used carefully.