Lines Matching full:extensions

143 Several OpenSSL commands can add extensions to a certificate or
151 This page uses \fBextensions\fR as the name of the section, when needed
178 String extensions simply have a string which contains either the value itself
181 Multi-valued extensions have a short form and a long form. The short form
191 \& [extensions]
212 \& [extensions]
225 \& [extensions]
237 \& [extensions]
245 The syntax of raw extensions is defined by the source code that parses
250 must be used, see the \*(L"\s-1ARBITRARY EXTENSIONS\*(R"\s0 section for more details.
251 .SH "STANDARD EXTENSIONS"
252 .IX Header "STANDARD EXTENSIONS"
415 \& [extensions]
511 \& [extensions]
550 \& [extensions]
599 \& [extensions]
682 .SH "DEPRECATED EXTENSIONS"
683 .IX Header "DEPRECATED EXTENSIONS"
684 The following extensions are non standard, Netscape specific and largely
686 .SS "Netscape String extensions"
687 .IX Subsection "Netscape String extensions"
690 Other extensions of this type are: \fBnsBaseUrl\fR,
695 This is a multi-valued extensions which consists of a list of flags to be
697 be used. The basicConstraints, keyUsage and extended key usage extensions are
702 .SH "ARBITRARY EXTENSIONS"
703 .IX Header "ARBITRARY EXTENSIONS"
706 format for supported extensions. Extreme care should be taken to ensure that
709 There are two ways to encode arbitrary extensions.
716 \& [extensions]
744 purposes prohibited by their extensions because a specific application does
745 not recognize or honour the values of the relevant extensions.
748 invalid extensions if they are not used carefully.