Lines Matching full:implementations
14 * is somewhat helpful. Basically, all implementations of all FIPS approved
27 * There is some ambiguity about whether all implementations of each algorithm
29 * implementation. To be safe we test all implementations, except ones that can
35 * implementations in the Python packages hashlib, pycryptodome, and
119 * The optional list of implementations to test. @func will be called
591 * because this module's implementations of AES-GCM won't actually be
598 * implementations of "cmac(aes)" such as "cmac-aes-ce", as they don't
605 /* "cmac" template with all "aes" implementations */
609 /* All standalone implementations of "cmac(aes)" */
633 * implementations of "ecb(aes)" such as "ecb-aes-ce", as they don't
640 /* "ecb" template with all "aes" implementations */
644 /* All standalone implementations of "ecb(aes)" */
669 * This does *not* apply to standalone implementations of these modes
670 * such as "cbc-aes-ce", as such implementations don't reuse another
672 * We must test all such standalone implementations.
677 * requirements for GCM being incompatible with GCM implementations that
685 /* All standalone implementations of "cbc(aes)" */
703 /* All standalone implementations of "cts(cbc(aes))" */
729 /* All standalone implementations of "ctr(aes)" */
747 /* All standalone implementations of "xts(aes)" */
765 /* All standalone implementations of "gcm(aes)" */
773 /* The GCM implementations assume an IV size of 12. */
788 /* All implementations of "sha1" */
801 * Tests for all SHA-256 implementations other than the sha256() library
803 * corresponding SHA-224 implementations.
808 /* All implementations of "sha256" */
837 * Tests for all SHA-512 implementations. As per the IG, these tests
838 * also fulfill the tests for the corresponding SHA-384 implementations.
843 /* All implementations of "sha512" */
961 * If no implementations were specified, then just test the default one. in fips_run_test()
962 * Otherwise, test the specified list of implementations. in fips_run_test()