| /NextBSD/crypto/openssl/doc/crypto/ |
| HD | OpenSSL_add_all_algorithms.pod | 6 add algorithms to internal table 20 OpenSSL keeps an internal table of digest algorithms and ciphers. It uses 23 OpenSSL_add_all_digests() adds all digest algorithms to the table. 25 OpenSSL_add_all_algorithms() adds all algorithms to the table (digests and 28 OpenSSL_add_all_ciphers() adds all encryption algorithms to the table including 29 password based encryption algorithms. 42 An application does not need to add algorithms to use them explicitly, for example 44 needs to lookup algorithms. 48 cannot find algorithms. This includes the PEM, PKCS#12, SSL and S/MIME libraries. 51 Calling OpenSSL_add_all_algorithms() links in all algorithms: as a result a
|
| HD | evp.pod | 29 asymmetric algorithms. To create a new EVP_PKEY see 66 All the symmetric algorithms (ciphers), digests and asymmetric algorithms 67 (public key algorithms) can be replaced by L<ENGINE|engine(3)> modules providing alternative 73 Although low level algorithm specific functions exist for many algorithms 75 versions of new algorithms cannot be accessed using the low level functions. 76 Also makes code harder to adapt to new algorithms and some options are not
|
| HD | CMS_add1_signer.pod | 42 algorithms are needed. New attributes can also be added using the returned 78 algorithms in preference order: 256 bit AES, Gost R3411-94, Gost 28147-89, 192 80 If any of these algorithms is not available then it will not be included: for example the GOST algo…
|
| HD | PKCS7_sign_add_signer.pod | 37 algorithms are needed. 65 algorithms: triple DES, 128 bit RC2, 64 bit RC2, DES and 40 bit RC2. If any of 66 these algorithms is disabled then it will not be included.
|
| HD | EVP_VerifyInit.pod | 52 Due to the link between message digests and public key algorithms the correct 54 algorithms and associated public key algorithms appears in
|
| HD | d2i_PKCS8PrivateKey.pod | 35 PKCS#5 v1.5 and PKCS#5 v2.0 password based encryption algorithms. 44 unknown algorithms will occur if an attempt is made to decrypt a private key.
|
| HD | EVP_DigestInit.pod | 132 return B<NID_sha1WithRSAEncryption>. Since digests and signature algorithms 139 and RIPEMD160 digest algorithms respectively. 142 algorithms but using DSS (DSA) for the signature algorithm. Note: there is 180 New applications should use the SHA2 digest algorithms such as SHA256. 181 The other digest algorithms are still in common use. 275 The link between digests and signing algorithms was fixed in OpenSSL 1.0 and
|
| HD | EVP_SignInit.pod | 61 Due to the link between message digests and public key algorithms the correct 63 algorithms and associated public key algorithms appears in
|
| HD | crypto.pod | 12 algorithms used in various Internet standards. The services provided 20 individual algorithms.
|
| HD | CMS_sign.pod | 57 algorithms in preference order: 256 bit AES, Gost R3411-94, Gost 28147-89, 192 59 If any of these algorithms is not available then it will not be included: for example the GOST algo…
|
| /NextBSD/crypto/openssl/doc/apps/ |
| HD | speed.pod | 39 This command is used to test the performance of cryptographic algorithms. 50 for all available algorithms. 52 =item B<[zero or more test algorithms]> 54 If any options are given, B<speed> tests those algorithms, otherwise all of
|
| HD | pkcs8.pod | 31 format with a variety of PKCS#5 (v1.5 and v2.0) and PKCS#12 algorithms. 110 This option enables the use of PKCS#5 v2.0 algorithms. Normally PKCS#8 114 the B<-v2> option PKCS#5 v2.0 algorithms are used which can use any 131 list of possible algorithms is included below. 138 for all available algorithms. 155 Private keys encrypted using PKCS#5 v2.0 algorithms and high iteration 163 Some software may use PKCS#12 password based encryption algorithms 171 =head1 PKCS#5 v1.5 and PKCS#12 algorithms. 173 Various algorithms can be used with the B<-v1> command line option, 181 These algorithms were included in the original PKCS#5 v1.5 specification. [all …]
|
| HD | ciphers.pod | 31 authentication, encryption and mac algorithms used along with any key size 76 algorithms. 81 algorithms. 142 "low" encryption cipher suites, currently those using 64 or 56 bit encryption algorithms 147 export encryption algorithms. Including 40 and 56 bits algorithms. 151 40 bit export encryption algorithms 155 56 bit export encryption algorithms. In OpenSSL 0.9.8c and later the set of 168 DH algorithms and anonymous ECDH algorithms. These cipher suites are vulnerable 247 FORTEZZA algorithms. Not implemented. 307 (needs an engine supporting GOST algorithms). [all …]
|
| HD | openssl.pod | 15 …ist-cipher-commands> | B<list-cipher-algorithms> | B<list-message-digest-algorithms> | B<list-publ… 49 The pseudo-commands B<list-cipher-algorithms> and 50 B<list-message-digest-algorithms> list all cipher and message digest names, one entry per line. Ali… 54 The pseudo-command B<list-public-key-algorithms> lists all supported public 55 key algorithms. 417 The B<list->I<XXX>B<-algorithms> pseudo-commands were added in OpenSSL 1.0.0;
|
| HD | dgst.pod | 87 This engine is not used as source for digest algorithms, unless it is 121 algorithm is HMAC (hash-based MAC), but there are other MAC algorithms 157 enable use of non-FIPS algorithms such as MD5 even in FIPS mode. 197 A source of random numbers is required for certain signing algorithms, in
|
| HD | pkcs12.pod | 110 output additional information about the PKCS#12 file structure, algorithms used and 220 (as output by the B<list-cipher-algorithms> command is specified then it 222 use PKCS#12 algorithms. 241 these options affect the iteration counts on the MAC and key algorithms. 307 The B<-keypbe> and B<-certpbe> algorithms allow the precise encryption 308 algorithms for private keys and certificates to be specified. Normally 312 description of all algorithms is contained in the B<pkcs8> manual page.
|
| /NextBSD/tools/tools/crypto/ |
| HD | cryptotest.c | 120 } algorithms[] = { variable 167 for (i = 0; i < nitems(algorithms); i++) in getalgbycode() 168 if (cipher == algorithms[i].code) in getalgbycode() 169 return &algorithms[i]; in getalgbycode() 178 for (i = 0; i < nitems(algorithms); i++) in getalgbyname() 179 if (streq(name, algorithms[i].name)) in getalgbyname() 180 return &algorithms[i]; in getalgbyname() 593 for (i = 0; i < nitems(algorithms); i++) { in main() 595 alg = &algorithms[i]; in main()
|
| /NextBSD/crypto/openssl/engines/ccgost/ |
| HD | README.gost | 6 support, new algorithms can be added even without recompilation of 11 GOST R 34.10-94 and GOST R 34.10-2001 - digital signature algorithms. 13 details of VKO key exchange algorithm. These algorithms use 15 2001 (which is elliptic-curve based). Key exchange algorithms 26 algorithms out there are based on hash functions using HMAC 35 This engine is designed to allow usage of this algorithms in the 38 See RFC 4490 for S/MIME with GOST algorithms and RFC 4491 for PKI. 84 default_algorithms parameter specifies that all algorithms, provided by 114 Paramset for both algorithms 0 is the test paramset which should be used 136 If you want to send encrypted mail using GOST algorithms, don't forget [all …]
|
| /NextBSD/crypto/openssl/doc/ssl/ |
| HD | SSL_check_chain.pod | 34 B<CERT_PKEY_CA_SIGNATURE>: the signature algorithms of all CA certificates 44 algorithms extension). 67 algorithms may also wish to check B<CERT_PKEY_CA_SIGNATURE> too. If no 75 Since the supported signature algorithms extension is only used in TLS 1.2
|
| HD | SSL_CONF_cmd.pod | 40 This sets the supported signature algorithms for TLS v1.2. For clients this 41 value is used directly for the supported signature algorithms extension. For 42 servers it is used to determine which signature algorithms to support. 44 The B<value> argument should be a colon separated list of signature algorithms 50 If this option is not set then all signature algorithms supported by the 55 This sets the supported signature algorithms associated with client 57 signature algorithms field of a certificate request. For clients it is 211 This sets the supported signature algorithms for TLS v1.2. For clients this 212 value is used directly for the supported signature algorithms extension. For 213 servers it is used to determine which signature algorithms to support. [all …]
|
| HD | SSL_library_init.pod | 6 - initialize SSL library by registering algorithms 48 OpenSSL 0.9.8o and 1.0.0a and later added SHA2 algorithms to SSL_library_init().
|
| /NextBSD/contrib/opie/libopie/ |
| HD | parsechallenge.c | 31 static struct algorithm algorithms[] = { variable 48 for (a = algorithms; a->name && strncmp(buffer, a->name, (int)(c - buffer)); a++);
|
| /NextBSD/sys/geom/mirror/ |
| HD | g_mirror.h | 410 static const char *algorithms[] = { in balance_name() local 422 return (algorithms[balance]); in balance_name() 428 static const char *algorithms[] = { in balance_id() local 438 if (strcmp(name, algorithms[n]) == 0) in balance_id()
|
| /NextBSD/crypto/openssh/ |
| HD | PROTOCOL | 36 1.3. transport: New public key algorithms "ssh-rsa-cert-v00@openssh.com", 42 OpenSSH introduces new public key algorithms to support certificate 54 1.5 transport: Protocol 2 Encrypt-then-MAC MAC algorithms 56 OpenSSH supports MAC algorithms, whose names contain "-etm", that 65 Specifically, the "-etm" MAC algorithms modify the transport protocol 88 AES-GCM is only negotiated as the cipher algorithms 91 the exchanged MAC algorithms are ignored and there doesn't have to be
|
| /NextBSD/crypto/openssl/doc/HOWTO/ |
| HD | keys.txt | 6 Keys are the basis of public key algorithms and PKI. Keys usually 13 algorithms. The most popular ones associated with certificates are
|