Lines Matching refs:not
5 the changes should not affect the default provider.
24 - An approved algorithm is not considered to be an approved implementation if it does not have a CA…
26 …zes an approved cryptographic algorithm, security function or process in an approved manner or not.
27 …ave added a table in their security policy called ‘Non-Approved Algorithms not allowed in the appr…
35 - If the per algorithm context value is not set, then the Configuration file option is used.
43 The following rules will apply to any code that currently is not FIPS approved,
188 turn off FIPS mode. This will not be added at this stage.
216 *dst = *src then it is not required.
266 There are a few places where we do not enforce key size that need to be addressed.
277 …If we chose not to remove them , then we need to check that OSSL_PKEY_PARAM_USE_COFACTOR_ECDH is s…
279 - X25519/X448 is not approved currently. keygen and keyexchange would also need an indicator if we …
286 - ECDSA Verify using prehashed message is not allowed.
295 - X963KDF (SHA1 is not allowed)
308 Note many of these (such as KDF's will not support SHAKE).
312 KECCAK-KMAC-128 and KECCAK-KMAC-256 should not be allowed for anything other than KMAC.
315 Test that Deterministic ECDSA does not allow SHAKE (IG C.K Additional Comments 6)
333 - TEST_RAND is not approved.