Home
last modified time | relevance | path

Searched refs:security (Results 1 – 25 of 98) sorted by relevance

1234

/openssl/doc/man3/
H A DSSL_CTX_set_security_level.pod42 the security level to B<level>. If not set the library default security level
46 retrieve the current security level.
62 If an application doesn't set its own security callback the default
75 The security level corresponds to a minimum of 80 bits of security. Any
100 Security level set to 192 bits of security. As a result RSA, DSA and
129 The bits of security limits affect all relevant parameters including
136 See SP800-57 for how the security limits are related to individual
139 Some security levels require large key sizes for non-ECC public key
144 offering insufficient security are not sent by the client and will not
161 represents the security level with B<SSL_CTX> or B<SSL>, respectively.
[all …]
H A DBN_security_bits.pod5 BN_security_bits - returns bits of security based on given numbers
15 BN_security_bits() returns the number of bits of security provided by a
16 specific algorithm and a particular key size. The bits of security is
20 parameters B<L> and B<N> are used to decide the bits of security, where
27 Number of security bits.
H A DOPENSSL_s390xcap.pod72 # 17 1<<46 message-security assist
75 # 76 1<<51 message-security assist extension 3
76 # 77 1<<50 message-security assist extension 4
77 # 86 1<<41 message-security-assist extension 12
82 #146 1<<45 message-security assist extension 8
83 #155 1<<36 message-security assist extension 9
H A DRSA_size.pod5 RSA_size, RSA_bits, RSA_security_bits - get RSA modulus size or security bits
35 RSA_security_bits() returns the number of security bits of the given B<rsa>
44 RSA_security_bits() returns the number of security bits.
H A DDH_size.pod6 security bits
36 DH_security_bits() returns the number of security bits of the given B<dh>
47 DH_security_bits() returns the number of security bits, or -1 if
H A DDSA_size.pod5 DSA_size, DSA_bits, DSA_security_bits - get DSA signature size, key bits or security bits
34 DSA_security_bits() returns the number of security bits of the given I<dsa>
39 DSA_security_bits() returns the number of security bits in the key, or -1 if
H A DX509_VERIFY_PARAM_set_flags.pod121 X509_VERIFY_PARAM_set_auth_level() sets the authentication security level to
123 The authentication security level determines the acceptable signature and public
126 must meet the specified security level.
127 The signature algorithm security level is not enforced for the chain's I<trust
132 The default security level is -1, or "not set".
133 At security level 0 or lower all algorithms are acceptable.
134 Security level 1 requires at least 80-bit-equivalent security and is broadly
240 X509_VERIFY_PARAM_get_auth_level() returns the current authentication security
258 purposes can be a security risk. Finer control over which extensions are
293 add any additional security but in some cases applications might want to
[all …]
H A DSSL_CTX_set1_sigalgs.pod72 Signature algorithms will neither be advertised nor used if the security level
73 prohibits them (for example SHA1 if the security level is 4 or more).
86 The use of MD5 as a digest is strongly discouraged due to security weaknesses.
H A DX509_get0_signature.pod75 the public key algorithm to B<*pknid>, the effective security bits to
92 The security bits returned by X509_get_signature_info() refers to information
94 cases the actual security of the signature is less because the signing
H A DSSL_alert_type_string.pod96 sender was unable to negotiate an acceptable set of security
179 versions might be avoided for security reasons). This message is
182 =item "IS"/"insufficient security"
212 satisfy a request; the process might receive security parameters
H A DEVP_PKEY_get_size.pod44 EVP_PKEY_get_security_bits() returns the number of security bits of the given
45 I<pkey>, bits of security is defined in NIST SP800-57.
H A DRAND_bytes.pod40 I<ctx> parameters. The bytes generated will have a security strength of at
51 By default, the OpenSSL CSPRNG supports a security level of 256 bits, provided it
H A DSSL_get_client_random.pod36 secret used to guarantee the security of the SSL/TLS session. This one
61 The security of your TLS session depends on keeping the master key secret:
H A DBN_rand.pod40 number of I<bits> in length and security strength at least I<strength> bits
62 number I<rnd>, of security strength at least I<strength> bits,
H A DEVP_aes_128_gcm.pod154 achieve AES 128-bit security, and XTS-AES-256 (B<EVP_aes_256_xts>) takes input
155 of a 512-bit key to achieve AES 256-bit security.
/openssl/test/recipes/30-test_defltfips/
H A Dfipsmodule.cnf6 security-checks = 1
/openssl/doc/man5/
H A Dfips_config.pod82 enforcement of FIPS security parameters such as minimum security strength of
93 =item B<security-checks>
213 security-checks = 1
/openssl/providers/common/der/
H A DNIST.asn19 -- Taken from https://csrc.nist.gov/projects/computer-security-objects-register/algorithm-registrat…
H A DDSA.asn124 -- Taken from https://csrc.nist.gov/projects/computer-security-objects-register/algorithm-registrat…
H A DDIGESTS.asn126 -- From https://csrc.nist.gov/projects/computer-security-objects-register/algorithm-registration
/openssl/doc/man1/
H A Dopenssl-dgst.pod.in93 since the default values are set to only supply half of the maximum security
97 16 (bytes) which results in a security strength of only 64 bits. To ensure the
98 maximum security strength of 128 bits, the xoflen should be set to at least 32.
101 32 (bytes) which results in a security strength of only 128 bits. To ensure the
102 maximum security strength of 256 bits, the xoflen should be set to at least 64.
/openssl/doc/man7/
H A DEVP_MD-SHAKE.pod77 For SHAKE-128, to ensure the maximum security strength of 128 bits, the output
80 For SHAKE-256, to ensure the maximum security strength of 256 bits, the output
/openssl/doc/designs/
H A Dfips_indicator.md21 …mode of operation that requires at least one service to use an approved security function (defined…
22 …e requires a built-in service indicator capable of indicating the use of approved security services
26 …on of whether the service utilizes an approved cryptographic algorithm, security function or proce…
27 …e updates related to indicators. AWS/google have added a table in their security policy called ‘No…
139 - Existing security check changes
334 - SSKDF The security policy needs to be specific about what it supports i.e. hash, kmac 128/256, h…
/openssl/
H A DNEWS.md818 * New security levels
1285 * Fix for security issue ([CVE-2011-0014])
1289 * Fix for security issue ([CVE-2010-4180])
1293 * Corrected fix for security issue ([CVE-2010-3864]).
1297 * Fix for security issue ([CVE-2010-3864]).
1303 * Fix for security issue ([CVE-2010-1633]).
1360 * Fix security issue ([CVE-2008-5077])
1570 * Security: Important security related bugfixes.
1639 * Important security related bugfixes.
1665 * Important security related bugfixes.
[all …]
/openssl/dev/release-aux/
H A Dopenssl-announce-pre-release.tmpl13 It should NOT be used for security critical purposes.

Completed in 41 milliseconds

1234