| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | OSSL_PROVIDER-default.7 | 180 .IP "\s-1SHA1,\s0 see \s-1\fBEVP_MD\-SHA1\s0\fR\|(7)" 4
183 .IP "\s-1SHA2,\s0 see \s-1\fBEVP_MD\-SHA2\s0\fR\|(7)" 4
185 .IP "\s-1SHA3,\s0 see \s-1\fBEVP_MD\-SHA3\s0\fR\|(7)" 4
187 .IP "KECCAK-KMAC, see \s-1\fBEVP_MD\-KECCAK\-KMAC\s0\fR\|(7)" 4
189 .IP "\s-1SHAKE,\s0 see \s-1\fBEVP_MD\-SHAKE\s0\fR\|(7)" 4
191 .IP "\s-1BLAKE2,\s0 see \s-1\fBEVP_MD\-BLAKE2\s0\fR\|(7)" 4
193 .IP "\s-1SM3,\s0 see \s-1\fBEVP_MD\-SM3\s0\fR\|(7)" 4
195 .IP "\s-1MD5,\s0 see \s-1\fBEVP_MD\-MD5\s0\fR\|(7)" 4
197 .IP "\s-1MD5\-SHA1,\s0 see \s-1\fBEVP_MD\-MD5\-SHA1\s0\fR\|(7)" 4
199 .IP "\s-1RIPEMD160,\s0 see \s-1\fBEVP_MD\-RIPEMD160\s0\fR\|(7)" 4
[all …]
|
| H A D | migration_guide.7 | 165 OpenSSL 3.0 such as the availability of the \s-1FIPS\s0 module.
175 \fIProviders and \s-1FIPS\s0 support\fR
188 One of the standard providers available is the \s-1FIPS\s0 provider. This makes
189 available \s-1FIPS\s0 validated cryptographic algorithms.
190 The \s-1FIPS\s0 provider is disabled by default and needs to be enabled explicitly
192 the \s-1FIPS\s0 provider gets built and installed in addition to the other standard
195 special purpose of installing only the \s-1FIPS\s0 provider into an existing
199 If the application code uses any digest or cipher algorithm via the \s-1EVP\s0 interface,
206 See also \*(L"Completing the installation of the \s-1FIPS\s0 Module\*(R" and
207 \&\*(L"Using the \s-1FIPS\s0 Module in applications\*(R".
[all …]
|
| H A D | OSSL_PROVIDER-FIPS.7 | 143 The OpenSSL \s-1FIPS\s0 provider is a special provider that conforms to the Federal
144 Information Processing Standards (\s-1FIPS\s0) specified in \s-1FIPS 140\-2.\s0 This 'module'
168 The \*(L"fips=yes\*(R" property can be use to make sure only \s-1FIPS\s0 approved
170 other non-crypto support operations that are not in the \s-1FIPS\s0 provider,
175 The OpenSSL \s-1FIPS\s0 provider supports these operations and algorithms:
178 .IP "\s-1SHA1,\s0 see \s-1\fBEVP_MD\-SHA1\s0\fR\|(7)" 4
181 .IP "\s-1SHA2,\s0 see \s-1\fBEVP_MD\-SHA2\s0\fR\|(7)" 4
183 .IP "\s-1SHA3,\s0 see \s-1\fBEVP_MD\-SHA3\s0\fR\|(7)" 4
185 .IP "KECCAK-KMAC, see \s-1\fBEVP_MD\-KECCAK\-KMAC\s0\fR\|(7)" 4
190 .IP "\s-1AES,\s0 see \s-1\fBEVP_CIPHER\-AES\s0\fR\|(7)" 4
[all …]
|
| H A D | provider-kdf.7 | 178 The \s-1KDF\s0 operation enables providers to implement \s-1KDF\s0 algorithms and make
179 them available to applications via the \s-1API\s0 functions \fBEVP_KDF_CTX_reset\fR\|(3),
183 \&\fIlibcrypto\fR and the provider in \s-1\fBOSSL_DISPATCH\s0\fR\|(3) arrays via
184 \&\s-1\fBOSSL_ALGORITHM\s0\fR\|(3) arrays that are returned by the provider's
190 function pointer from an \s-1\fBOSSL_DISPATCH\s0\fR\|(3) element named
200 \&\s-1\fBOSSL_DISPATCH\s0\fR\|(3) array entries are identified by numbers that are provided as
220 A \s-1KDF\s0 algorithm implementation may not implement all of these functions.
228 structure for holding context information during a \s-1KDF\s0 operation.
229 A pointer to this context will be passed back in a number of the other \s-1KDF\s0
234 \&\fBOSSL_FUNC_kdf_freectx()\fR is passed a pointer to the provider side \s-1KDF\s0 context in
[all …]
|
| H A D | EVP_PKEY-DH.7 | 144 For \fB\s-1DH\s0\fR \s-1FFC\s0 key agreement, two classes of domain parameters can be used:
150 See \s-1\fBEVP_PKEY\-FFC\s0\fR\|(7) for more information about \s-1FFC\s0 keys.
152 The \fB\s-1DH\s0\fR key type uses PKCS#3 format which saves \fIp\fR and \fIg\fR, but not the
154 The \fB\s-1DHX\s0\fR key type uses X9.42 format which saves the value of \fIq\fR and this
155 must be used for \s-1FIPS186\-4.\s0 If key validation is required, users should be aware
156 of the nuances associated with \s-1FIPS186\-4\s0 style parameters as discussed in
157 \&\*(L"\s-1DH\s0 key validation\*(R".
158 .SS "\s-1DH\s0 and \s-1DHX\s0 domain parameters"
160 In addition to the common \s-1FCC\s0 parameters that all \s-1FFC\s0 keytypes should support
161 (see \*(L"\s-1FFC\s0 parameters\*(R" in \s-1\fBEVP_PKEY\-FFC\s0\fR\|(7)) the \fB\s-1DHX\s0\fR and \…
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | ASN1_aux_cb.3 | 179 \&\s-1ASN.1\s0 data structures can be associated with an \fB\s-1ASN1_AUX\s0\fR object to supply
180 additional information about the \s-1ASN.1\s0 structure. An \fB\s-1ASN1_AUX\s0\fR structure is
181 associated with the structure during the definition of the \s-1ASN.1\s0 template. For
182 example an \fB\s-1ASN1_AUX\s0\fR structure will be associated by using one of the various
183 \&\s-1ASN.1\s0 template definition macros that supply auxiliary information such as
187 An \fB\s-1ASN1_AUX\s0\fR structure contains the following information.
195 The \fB\s-1ASN1_AFLG_REFCOUNT\s0\fR flag indicates that objects support reference counting.
197 The \fB\s-1ASN1_AFLG_ENCODING\s0\fR flag indicates that the original encoding of the
200 The \fB\s-1ASN1_AFLG_BROKEN\s0\fR flag is a work around for broken encoders where the
203 The \fB\s-1ASN1_AFLG_CONST_CB\s0\fR flag indicates that the \*(L"const\*(R" form of the
[all …]
|
| H A D | ASN1_generate_nconf.3 | 151 These functions generate the \s-1ASN1\s0 encoding of a string
152 in an \fB\s-1ASN1_TYPE\s0\fR structure.
159 functions. \fIcnf\fR or \fInconf\fR can be set to \s-1NULL\s0 if no additional
176 Unless otherwise specified only the \fB\s-1ASCII\s0\fR format is permissible.
177 .IP "\fB\s-1BOOLEAN\s0\fR, \fB\s-1BOOL\s0\fR" 4
180 should be \fB\s-1TRUE\s0\fR or \fB\s-1FALSE\s0\fR. Additionally \fB\s-1TRUE\s0\fR, \fBtrue\fR, \fBY…
181 \&\fBy\fR, \fB\s-1YES\s0\fR, \fByes\fR, \fB\s-1FALSE\s0\fR, \fBfalse\fR, \fBN\fR, \fBn\fR, \fB\s-1N…
183 .IP "\fB\s-1NULL\s0\fR" 4
185 Encode the \fB\s-1NULL\s0\fR type, the \fIvalue\fR string must not be present.
186 .IP "\fB\s-1INTEGER\s0\fR, \fB\s-1INT\s0\fR" 4
[all …]
|
| H A D | EVP_EncryptInit.3 | 367 hidden entirely by defining \fB\s-1OPENSSL_API_COMPAT\s0\fR with a suitable version value,
375 hidden entirely by defining \fB\s-1OPENSSL_API_COMPAT\s0\fR with a suitable version value,
383 The \s-1EVP\s0 cipher routines are a high-level interface to certain
386 The \fB\s-1EVP_CIPHER\s0\fR type is a structure for cipher method implementation.
391 See \*(L"\s-1ALGORITHM FETCHING\*(R"\s0 in \fBcrypto\fR\|(7) for further information.
395 Fetched \fB\s-1EVP_CIPHER\s0\fR structures are reference counted.
398 Increments the reference count for an \fB\s-1EVP_CIPHER\s0\fR structure.
401 Decrements the reference count for the fetched \fB\s-1EVP_CIPHER\s0\fR structure.
423 If this function happens to be used with a fetched \fB\s-1EVP_CIPHER\s0\fR, it will
424 translate the controls that are known to OpenSSL into \s-1\fBOSSL_PARAM\s0\fR\|(3)
[all …]
|
| H A D | DEFINE_STACK_OF.3 | 205 functions that wrap around the utility \fBOPENSSL_sk_\fR \s-1API.\s0
206 In the description here, \fB\f(BI\s-1TYPE\s0\fB\fR is used
209 The \s-1\fBSTACK_OF\s0()\fR macro returns the name for a stack of the specified \fB\f(BI\s-1TYPE\s0…
212 There are several \fB\s-1DEFINE...\s0\fR macros that create static inline functions
217 \&\s-1\fBDEFINE_STACK_OF\s0()\fR creates set of functions for a stack of \fB\f(BI\s-1TYPE\s0\fB\fR …
219 \&\fB\s-1STACK_OF\s0\fR(\fB\f(BI\s-1TYPE\s0\fB\fR) and each function name begins with \fBsk_\f(BI\s…
220 \&\s-1\fBDEFINE_STACK_OF_CONST\s0()\fR is identical to \s-1\fBDEFINE_STACK_OF\s0()\fR except
230 \&\s-1\fBDEFINE_SPECIAL_STACK_OF\s0()\fR and \s-1\fBDEFINE_SPECIAL_STACK_OF_CONST\s0()\fR are simil…
231 except \fB\s-1FUNCNAME\s0\fR is used in the function names:
240 \&\fBsk_\f(BI\s-1TYPE\s0\fB_num\fR() returns the number of elements in \fIsk\fR or \-1 if \fIsk\fR …
[all …]
|
| H A D | EVP_PKEY_CTX_ctrl.3 | 316 hidden entirely by defining \fB\s-1OPENSSL_API_COMPAT\s0\fR with a suitable version value,
340 For \fIcmd\fR = \fB\s-1EVP_PKEY_CTRL_SET_MAC_KEY\s0\fR, \fIp1\fR is the length of the \s-1MAC\s0 ke…
341 and \fIp2\fR is the \s-1MAC\s0 key. This is used by Poly1305, SipHash, \s-1HMAC\s0 and \s-1CMAC.\s0
360 in a signature. It can be used in the \s-1RSA, DSA\s0 and \s-1ECDSA\s0 algorithms.
363 in a signature. It can be used in the \s-1RSA, DSA\s0 and \s-1ECDSA\s0 algorithms.
377 key generation. For example for \s-1EC\s0 keys this will set the curve name and for
378 \&\s-1DH\s0 keys it will set the name of the finite field group.
383 terminating \s-1NUL\s0 byte.
384 .SS "\s-1RSA\s0 parameters"
386 \&\fBEVP_PKEY_CTX_set_rsa_padding()\fR sets the \s-1RSA\s0 padding mode for \fIctx\fR.
[all …]
|
| H A D | SSL_CTX_set_options.3 | 181 The behaviour of the \s-1SSL\s0 library can be changed by setting several options.
186 protocol behaviour of the \s-1SSL\s0 library. The (internal) behaviour of
187 the \s-1API\s0 can be changed by using the similar
190 During a handshake, the option settings of the \s-1SSL\s0 object are used. When
191 a new \s-1SSL\s0 object is created from a context using \fBSSL_new()\fR, the current
193 \&\s-1SSL\s0 objects. \fBSSL_clear()\fR does not affect the settings.
196 .IP "\s-1SSL_OP_CRYPTOPRO_TLSEXT_BUG\s0" 4
199 when \s-1GOST\s0 ciphersuite is negotiated. Required for interoperability with CryptoPro
200 \&\s-1CSP 3\s0.x.
201 .IP "\s-1SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS\s0" 4
[all …]
|
| H A D | OSSL_CMP_CTX_new.3 | 302 This is the context \s-1API\s0 for using \s-1CMP\s0 (Certificate Management Protocol) with
305 \&\fBOSSL_CMP_CTX_new()\fR allocates an \fB\s-1OSSL_CMP_CTX\s0\fR structure associated with
307 both of which may be \s-1NULL\s0 to select the defaults.
309 the logging verbosity is set to \s-1OSSL_CMP_LOG_INFO,\s0
311 and the proof-of-possession method is set to \s-1OSSL_CRMF_POPO_SIGNATURE.\s0
313 \&\fBOSSL_CMP_CTX_free()\fR deallocates an \s-1OSSL_CMP_CTX\s0 structure.
316 clearing the internal \s-1CMP\s0 transaction (aka session) status, PKIStatusInfo,
320 All other field values (i.e., \s-1CMP\s0 options) are retained for potential reuse.
323 (e.g., \s-1OSSL_CMP_OPT_IMPLICIT_CONFIRM\s0) in the given \s-1OSSL_CMP_CTX\s0 structure.
326 .IP "\fB\s-1OSSL_CMP_OPT_LOG_VERBOSITY\s0\fR" 4
[all …]
|
| H A D | d2i_RSAPrivateKey.3 | 198 hidden entirely by defining \fB\s-1OPENSSL_API_COMPAT\s0\fR with a suitable version value,
242 All functions described here are deprecated. Please use \s-1\fBOSSL_DECODER\s0\fR\|(3)
243 instead of the \fBd2i\fR functions and \s-1\fBOSSL_ENCODER\s0\fR\|(3) instead of the \fBi2d\fR
246 In the description here, \fB\f(BI\s-1TYPE\s0\fB\fR is used a placeholder for any of the
247 OpenSSL datatypes, such as \fB\s-1RSA\s0\fR.
255 because the PKCS#1 \fB\s-1RSA\s0\fR structure doesn't include any key parameters.
257 \&\fBd2i_\f(BI\s-1TYPE\s0\fBPrivateKey\fR() and derivates thereof decode \s-1DER\s0 encoded
258 \&\fB\f(BI\s-1TYPE\s0\fB\fR private key data organized in a type specific structure.
260 \&\fBd2i_\f(BI\s-1TYPE\s0\fBPublicKey\fR() and derivates thereof decode \s-1DER\s0 encoded
261 \&\fB\f(BI\s-1TYPE\s0\fB\fR public key data organized in a type specific structure.
[all …]
|
| H A D | UI_STRING.3 | 176 The \fB\s-1UI_STRING\s0\fR gets created internally and added to a \fB\s-1UI\s0\fR whenever
182 For a \fB\s-1UI_METHOD\s0\fR user, there's no need to know more.
183 For a \fB\s-1UI_METHOD\s0\fR creator, it is of interest to fetch text from these
184 \&\fB\s-1UI_STRING\s0\fR objects as well as adding results to some of them.
187 \&\fB\s-1UI_STRING\s0\fR.
190 given \fB\s-1UI_STRING\s0\fR.
196 associated with a \fB\s-1UIT_BOOLEAN\s0\fR type \fB\s-1UI_STRING\s0\fR.
197 For all other \fB\s-1UI_STRING\s0\fR types, \s-1NULL\s0 is returned.
202 This is only useful for \fB\s-1UIT_PROMPT\s0\fR and \fB\s-1UIT_VERIFY\s0\fR type strings.
203 For all other \fB\s-1UI_STRING\s0\fR types, \fBUI_get0_result_string()\fR returns \s-1NULL\s0
[all …]
|
| H A D | OSSL_HTTP_transfer.3 | 190 \&\fBOSSL_HTTP_open()\fR initiates an \s-1HTTP\s0 session using the \fIbio\fR argument if not
191 \&\s-1NULL,\s0 else by connecting to a given \fIserver\fR optionally via a \fIproxy\fR.
193 Typically the OpenSSL build supports sockets and the \fIbio\fR parameter is \s-1NULL.\s0
194 In this case \fIrbio\fR must be \s-1NULL\s0 as well and the \fIserver\fR must be non-NULL.
195 The function creates a network \s-1BIO\s0 internally using \fBBIO_new_connect\fR\|(3)
197 defaulting to 80 for \s-1HTTP\s0 or 443 for \s-1HTTPS.\s0
198 Then this internal \s-1BIO\s0 is used for setting up a connection
200 If \fIbio\fR is given and \fIrbio\fR is \s-1NULL\s0 then this \fIbio\fR is used instead.
209 If \fIbio\fR is \s-1NULL\s0 the optional \fIproxy\fR parameter can be used to set an
210 \&\s-1HTTP\s0(S) proxy to use (unless overridden by \*(L"no_proxy\*(R" settings).
[all …]
|
| H A D | PEM_read_bio_PrivateKey.3 | 274 hidden entirely by defining \fB\s-1OPENSSL_API_COMPAT\s0\fR with a suitable version value,
332 …functions described on this page that have a \fI\s-1TYPE\s0\fR of \fB\s-1DH\s0\fR, \fB\s-1DSA\s0\fR
333 and \fB\s-1RSA\s0\fR are deprecated. Applications should use \fBOSSL_ENCODER_to_bio\fR\|(3) and
336 The \s-1PEM\s0 functions read or write structures in \s-1PEM\s0 format. In
337 this sense \s-1PEM\s0 format is simply base64 encoded data surrounded
341 \&\fB\s-1PEM FUNCTION ARGUMENTS\s0\fR section.
344 brevity the term "\fB\f(BI\s-1TYPE\s0\fB\fR functions" will be used below to collectively
345 refer to the \fBPEM_read_bio_\f(BI\s-1TYPE\s0\fB\fR(), \fBPEM_read_\f(BI\s-1TYPE\s0\fB\fR(),
346 \&\fBPEM_write_bio_\f(BI\s-1TYPE\s0\fB\fR(), and \fBPEM_write_\f(BI\s-1TYPE\s0\fB\fR() functions.
356 to the relevant \s-1PEM\s0 function. See the \*(L"\s-1EXAMPLES\*(R"\s0 section below.
[all …]
|
| H A D | ENGINE_add.3 | 186 hidden entirely by defining \fB\s-1OPENSSL_API_COMPAT\s0\fR with a suitable version value,
300 hidden entirely by defining \fB\s-1OPENSSL_API_COMPAT\s0\fR with a suitable version value,
312 form of \fB\s-1ENGINE\s0\fR objects. These objects act as containers for
317 The cryptographic functionality that can be provided by an \fB\s-1ENGINE\s0\fR
330 Due to the modular nature of the \s-1ENGINE API,\s0 pointers to ENGINEs need to be
332 the underlying \s-1ENGINE\s0 object. Ie. one should obtain a new reference when
333 making copies of an \s-1ENGINE\s0 pointer if the copies will be used (and
336 \&\s-1ENGINE\s0 objects have two levels of reference-counting to match the way in
337 which the objects are used. At the most basic level, each \s-1ENGINE\s0 pointer is
342 However, a structural reference provides no guarantee that the \s-1ENGINE\s0 is
[all …]
|
| H A D | SSL_CONF_cmd.3 | 154 configuration of \fB\s-1SSL_CTX\s0\fR or \fB\s-1SSL\s0\fR structures by providing a common
161 flag \fB\s-1SSL_CONF_FLAG_CMDLINE\s0\fR is set) are listed below. Note: all \fBoption\fR
167 Various bug workarounds are set, same as setting \fB\s-1SSL_OP_ALL\s0\fR.
170 Disables support for \s-1SSL/TLS\s0 compression, same as setting
171 \&\fB\s-1SSL_OP_NO_COMPRESSION\s0\fR.
175 Enables support for \s-1SSL/TLS\s0 compression, same as clearing
176 \&\fB\s-1SSL_OP_NO_COMPRESSION\s0\fR.
181 Disables support for session tickets, same as setting \fB\s-1SSL_OP_NO_TICKET\s0\fR.
186 Equivalent to \fB\s-1SSL_OP_CIPHER_SERVER_PREFERENCE\s0\fR. Only used by servers.
190 setting \fB\s-1SSL_OP_ALLOW_CLIENT_RENEGOTIATION\s0\fR.
[all …]
|
| H A D | OSSL_HTTP_REQ_CTX.3 | 190 \&\fB\s-1OSSL_HTTP_REQ_CTX\s0\fR is a context structure for an \s-1HTTP\s0 request and response,
193 This file documents low-level \s-1HTTP\s0 functions rarely used directly. High-level
194 \&\s-1HTTP\s0 client functions like \fBOSSL_HTTP_get\fR\|(3) and \fBOSSL_HTTP_transfer\fR\|(3)
197 \&\fBOSSL_HTTP_REQ_CTX_new()\fR allocates a new \s-1HTTP\s0 request context structure,
198 which gets populated with the \fB\s-1BIO\s0\fR to write/send the request to (\fIwbio\fR),
199 the \fB\s-1BIO\s0\fR to read/receive the response from (\fIrbio\fR, which may be equal to
202 the \fB\s-1OSSL_HTTP_DEFAULT_MAX_LINE_LEN\s0\fR of 4KiB should be used.
204 The allocated context structure includes an internal memory \fB\s-1BIO\s0\fR,
205 which collects the \s-1HTTP\s0 request header lines.
207 \&\fBOSSL_HTTP_REQ_CTX_free()\fR frees up the \s-1HTTP\s0 request context \fIrctx\fR.
[all …]
|
| /freebsd/secure/usr.bin/openssl/man/ |
| H A D | openssl-ciphers.1 | 166 ordered \s-1SSL\s0 cipher preference lists. It can be used to
188 \&\s-1PSK\s0 and \s-1SRP\s0 ciphers are not enabled by default: they require \fB\-psk\fR or \fB\-sr…
194 depending on the configured certificates and presence of \s-1DH\s0 parameters.
200 When combined with \fB\-s\fR includes cipher suites which require \s-1PSK.\s0
203 When combined with \fB\-s\fR includes cipher suites which require \s-1SRP.\s0 This option
247 It can consist of a single cipher suite such as \fB\s-1RC4\-SHA\s0\fR.
250 cipher suites of a certain type. For example \fB\s-1SHA1\s0\fR represents all ciphers
251 suites using the digest algorithm \s-1SHA1\s0 and \fBSSLv3\fR represents all \s-1SSL\s0 v3
256 \&\fB\s-1SHA1+DES\s0\fR represents all cipher suites containing the \s-1SHA1\s0 \fBand\fR the \s-1D…
284 The cipher list can be prefixed with the \fB\s-1DEFAULT\s0\fR keyword, which enables
[all …]
|
| H A D | openssl-cmp.1 | 231 \&\s-1TLS\s0 connection options:
280 Certificate verification options, for both \s-1CMP\s0 and \s-1TLS:\s0
315 Management Protocol (\s-1CMP\s0) as defined in \s-1RFC4210.\s0
316 It can be used to request certificates from a \s-1CA\s0 server,
318 request certificates to be revoked, and perform other types of \s-1CMP\s0 requests.
331 Section(s) to use within config file defining \s-1CMP\s0 options.
343 0 = \s-1EMERG, 1\s0 = \s-1ALERT, 2\s0 = \s-1CRIT, 3\s0 = \s-1ERR, 4\s0 = \s-1WARN, 5\s0 = \s-1NOTE,
344 6\s0 = \s-1INFO, 7\s0 = \s-1DEBUG, 8\s0 = \s-1TRACE.\s0
345 Defaults to 6 = \s-1INFO.\s0
350 \&\s-1CMP\s0 command to execute.
[all …]
|
| H A D | openssl-ocsp.1 | 143 .SS "\s-1OCSP\s0 Client"
164 [\fB\-url\fR \fI\s-1URL\s0\fR]
185 .SS "\s-1OCSP\s0 Server"
246 The Online Certificate Status Protocol (\s-1OCSP\s0) enables applications to
247 determine the (revocation) state of an identified certificate (\s-1RFC 2560\s0).
249 This command performs many common \s-1OCSP\s0 tasks. It can be used
251 to an \s-1OCSP\s0 responder and behave like a mini \s-1OCSP\s0 server itself.
256 .SS "\s-1OCSP\s0 Client Options"
268 This option \fB\s-1MUST\s0\fR come before any \fB\-cert\fR options.
285 Sign the \s-1OCSP\s0 request using the certificate specified in the \fB\-signer\fR
[all …]
|
| H A D | openssl-s_server.1 | 156 [\fB\-certform\fR \fB\s-1DER\s0\fR|\fB\s-1PEM\s0\fR|\fBP12\fR]
162 [\fB\-keyform\fR \fB\s-1DER\s0\fR|\fB\s-1PEM\s0\fR|\fBP12\fR|\fB\s-1ENGINE\s0\fR]
165 [\fB\-dcertform\fR \fB\s-1DER\s0\fR|\fB\s-1PEM\s0\fR|\fBP12\fR]
168 [\fB\-dkeyform\fR \fB\s-1DER\s0\fR|\fB\s-1PEM\s0\fR|\fBP12\fR|\fB\s-1ENGINE\s0\fR]
192 [\fB\-CRLform\fR \fB\s-1DER\s0\fR|\fB\s-1PEM\s0\fR]
347 [\fB\-xcertform\fR \fB\s-1DER\s0\fR|\fB\s-1PEM\s0\fR]>
348 [\fB\-xkeyform\fR \fB\s-1DER\s0\fR|\fB\s-1PEM\s0\fR]>
363 This command implements a generic \s-1SSL/TLS\s0 server which
364 listens for connections on a given port using \s-1SSL/TLS.\s0
375 The \s-1TCP\s0 port to listen on for connections. If not specified 4433 is used.
[all …]
|
| H A D | openssl.1 | 148 \&\fBopenssl\fR \fBno\-\fR\fI\s-1XXX\s0\fR [ \fIoptions\fR ]
151 OpenSSL is a cryptography toolkit implementing the Secure Sockets Layer (\s-1SSL\s0
152 v2/v3) and Transport Layer Security (\s-1TLS\s0 v1) network protocols and related
172 the \*(L"\s-1SYNOPSIS\*(R"\s0 above).
180 The command \fBno\-\fR\fI\s-1XXX\s0\fR tests whether a command of the
181 specified name is available. If no command named \fI\s-1XXX\s0\fR exists, it
182 returns 0 (success) and prints \fBno\-\fR\fI\s-1XXX\s0\fR; otherwise it returns 1
183 and prints \fI\s-1XXX\s0\fR. In both cases, the output goes to \fBstdout\fR and
187 availability of ciphers in the \fBopenssl\fR program. (\fBno\-\fR\fI\s-1XXX\s0\fR is
189 \&\fBlist\fR, or \fBno\-\fR\fI\s-1XXX\s0\fR itself.)
[all …]
|
| /freebsd/lib/libc/arm/aeabi/ |
| H A D | aeabi_vfp_float.S | 36 LOAD_SREGS(s0, s1, r0, r1)
37 vcmp.f32 s0, s1
44 LOAD_SREGS(s0, s1, r0, r1)
45 vcmpe.f32 s0, s1
52 LOAD_SREGS(s0, s1, r0, r1)
53 vcmpe.f32 s1, s0
60 LOAD_SREGS(s0, s1, r0, r1)
61 vcmp.f32 s0, s1
71 LOAD_SREGS(s0, s1, r0, r1)
72 vcmp.f32 s0, s1
[all …]
|