Home
last modified time | relevance | path

Searched refs:test (Results 1 – 25 of 152) sorted by relevance

1234567

/mbedtls-latest/tests/suites/
Dtest_suite_cipher.ccm.data1 AES-128-CCM test vector NIST #1 (P=0, N=7, A=0, T=4)
5 AES-128-CCM test vector NIST #2 (P=0, N=7, A=0, T=4)
9 AES-128-CCM test vector NIST #3 (P=0, N=7, A=0, T=16)
13 AES-128-CCM test vector NIST #4 (P=0, N=7, A=0, T=16)
17 AES-128-CCM test vector NIST #5 (P=0, N=13, A=0, T=4)
21 AES-128-CCM test vector NIST #6 (P=0, N=13, A=0, T=4)
25 AES-128-CCM test vector NIST #7 (P=0, N=13, A=0, T=16)
29 AES-128-CCM test vector NIST #8 (P=0, N=13, A=0, T=16)
33 AES-128-CCM test vector NIST #9 (P=24, N=7, A=0, T=4)
37 AES-128-CCM test vector NIST #10 (P=24, N=7, A=0, T=4)
[all …]
Dtest_suite_gcm.camellia.data1 Camellia-GCM test vect draft-kato-ipsec-camellia-gcm #1 (128-en)
5 Camellia-GCM test vect draft-kato-ipsec-camellia-gcm #2 (128-en)
9 Camellia-GCM test vect draft-kato-ipsec-camellia-gcm #3 (128-en)
13 Camellia-GCM test vect draft-kato-ipsec-camellia-gcm #4 (128-en)
17 Camellia-GCM test vect draft-kato-ipsec-camellia-gcm #5 (128-en)
21 Camellia-GCM test vect draft-kato-ipsec-camellia-gcm #6 (128-en)
25 Camellia-GCM test vect draft-kato-ipsec-camellia-gcm #7 (192-en)
29 Camellia-GCM test vect draft-kato-ipsec-camellia-gcm #8 (192-en)
33 Camellia-GCM test vect draft-kato-ipsec-camellia-gcm #9 (192-en)
37 Camellia-GCM test vect draft-kato-ipsec-camellia-gcm #10 (192-en)
[all …]
Dtest_suite_lmots.data1 LMOTS sign-verify test #1
2 # This test uses a fixed message, and then generates a private key, signs the
6 LMOTS sign-verify test #2
7 # This test uses a fixed message, and then generates a private key, signs the
11 LMOTS NULL-message sign-verify test
12 # This test uses a NULL zero-length message, and then generates a private key,
16 LMOTS hsslms interop test #1
17 # This test uses data from https://github.com/pmvr/python-hsslms due to the
18 # limited amount of available test vectors for LMOTS, and few implementations
21 # This test uses the same OTS key as the LMS hsslms interop test 1 (leaf 0 of
[all …]
Dtest_suite_lms.data1 LMS sign-verify test
2 # This test uses a fixed message, and then generates a private key, signs the
6 LMS NULL-message sign-verify test
7 # This test uses a NULL zero-length message, and then generates a private key,
11 LMS pyhsslms interop test #1
12 # This test uses data from https://github.com/russhousley/pyhsslms due to the
13 # limited amount of available test vectors for LMS. The private key is stored in
19 # and the public key before including them in a the test data.
37 LMS pyhsslms interop test #2
38 # This test case continues from "LMS pyhsslms interop test #1".
[all …]
Dtest_suite_bignum.misc.data4 Base test mpi_read_write_string #1
7 Base test mpi_read_write_string #1 (Leading 0)
10 Base test mpi_read_write_string #2
13 Base test mpi_read_write_string #3 (Read zero decimal)
16 Base test mpi_read_write_string #3 (Read zero hex)
19 Base test mpi_read_write_string #3 (Read minus zero decimal)
22 Base test mpi_read_write_string #3 (Read minus zero hex)
25 Base test mpi_read_write_string #3 (Negative decimal)
28 Base test mpi_read_write_string #3 (Negative decimal, leading 0)
31 Base test mpi_read_write_string #3 (Negative hex -> decimal)
[all …]
Dtest_suite_psa_crypto_se_driver_hal_mocks.data1 SE init mock test: success
4 SE init mock test: failure
7 SE init mock test: invalid location (0)
10 SE init mock test: location not supported (INT_MAX)
13 SE key importing mock test
16 SE key importing mock test: max key bits
19 SE key importing mock test: more than max key bits
22 SE key importing mock test: alloc failed
25 SE key importing mock test: import failed
28 SE key exporting mock test
[all …]
Dtest_suite_ecdsa.data93 ECDSA deterministic test vector rfc 6979 p192 sha1 [#1]
97 ECDSA deterministic test vector rfc 6979 p192 sha224 [#1]
101 ECDSA deterministic test vector rfc 6979 p192 sha256 [#1]
105 ECDSA deterministic test vector rfc 6979 p192 sha384 [#1]
109 ECDSA deterministic test vector rfc 6979 p192 sha512 [#1]
113 ECDSA deterministic test vector rfc 6979 p192 sha1 [#2]
117 ECDSA deterministic test vector rfc 6979 p192 sha224 [#2]
121 ECDSA deterministic test vector rfc 6979 p192 sha256 [#2]
125 ECDSA deterministic test vector rfc 6979 p192 sha384 [#2]
129 ECDSA deterministic test vector rfc 6979 p192 sha512 [#2]
[all …]
Dtest_suite_psa_crypto_se_driver_hal.data4 # Run this test case a second time to verify that the library deinit
66 Key import smoke test: AES-CTR
69 Key import smoke test: AES-CBC
72 Key import smoke test: AES-CMAC
75 Key import smoke test: AES-CCM
78 Key import smoke test: AES-GCM
81 Key import smoke test: ARIA-CTR
84 Key import smoke test: ARIA-CBC
87 Key import smoke test: ARIA-CMAC
90 Key import smoke test: ARIA-CCM
[all …]
Dtest_suite_x509write.data63test-ca_unenc.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"01":"20190210144406":"202…
67test-ca_unenc.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"01":"19700210144406":"202…
71test-ca_unenc.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"01":"20190210144406":"205…
75test-ca_unenc.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"01":"19700210144406":"205…
79test-ca_unenc.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"01":"20500210144406":"205…
83test-ca_unenc.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"01":"20190210144406":"202…
87test-ca_unenc.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"01":"20110212144406":"202…
91test-ca_unenc.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"01":"20110212144406":"202…
95test-ca_unenc.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"01":"20190210144406":"202…
99test-ca_unenc.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"01":"20190210144406":"202…
[all …]
Dhelpers.function5 #include <test/arguments.h>
6 #include <test/helpers.h>
7 #include <test/macros.h>
8 #include <test/random.h>
9 #include <test/bignum_helpers.h>
10 #include <test/psa_crypto_helpers.h>
11 #include <test/threading_helpers.h>
42 #define DISPATCH_INVALID_TEST_DATA -4 /* Invalid test parameter type.
Dtest_suite_x509parse.data19 x509_cert_info:"../framework/data_files/parse_input/test-ca.crt":"cert. version \: 3\nserial nu…
23 x509_cert_info:"../framework/data_files/parse_input/test-ca.crt.der":"cert. version \: 3\nseria…
143 x509_cert_info:"../framework/data_files/parse_input/test-ca-any_policy.crt":"cert. version \: 3…
147 x509_cert_info:"../framework/data_files/parse_input/test-ca-any_policy_ec.crt":"cert. version \…
151 x509_cert_info:"../framework/data_files/parse_input/test-ca-any_policy_with_qualifier.crt":"cert. v…
155 x509_cert_info:"../framework/data_files/parse_input/test-ca-any_policy_with_qualifier_ec.crt":"cert…
159 x509_cert_info:"../framework/data_files/parse_input/test-ca-multi_policy.crt":"cert. version \:…
163 x509_cert_info:"../framework/data_files/parse_input/test-ca-multi_policy_ec.crt":"cert. version …
167 x509_cert_info:"../framework/data_files/parse_input/test-ca-unsupported_policy.crt":"cert. version …
171 x509_cert_info:"../framework/data_files/parse_input/test-ca-unsupported_policy_ec.crt":"cert. versi…
[all …]
Dmain_test.function120 * \brief Function pointer type for test function wrappers.
122 * A test function wrapper decodes the parameters and passes them to the
123 * underlying test function. Both the wrapper and the underlying function
136 * \brief Table of test function wrappers. Used by dispatch_test().
148 * \brief Dispatches test functions based on function index.
151 * \param params The array of parameters to pass to the test function.
187 * \brief Checks if test function is supported in this build-time
233 extern void (*mbedtls_test_hook_test_fail)(const char *test, int line, const char *file);
243 * the .datax file as well as data files used by test cases
248 * test-specific files such as the outcome file, which is arguably
Dtest_suite_test_helpers.function3 /* Test some parts of the test framework. */
5 #include <test/helpers.h>
6 #include <test/memory.h>
16 /* We can't test that poisoning makes the memory inaccessible:
18 * That negative testing is done in programs/test/metatest.c. */
/mbedtls-latest/docs/architecture/testing/
Dtest-framework.md1 # Mbed TLS test framework
3 This document is an overview of the Mbed TLS test framework and test tools.
11 ### Unit test descriptions
13test case has a description which succinctly describes for a human audience what the test does. Th…
16 …Rationale: keep the tools that process test descriptions (`generate_test_code.py`, [outcome file](…
18 …Rationale: make it easy to relate a failure log to the test data. Avoid confusion between cases in…
21 … lot of test cases with longer descriptions, but they should be avoided. At least please make sure…
22 …en” is even better if these inequalities and parities are why this particular test data was chosen.
23 * Avoid changing the description of an existing test case without a good reason. This breaks the tr…
31 #### SSL test case descriptions
[all …]
Dinvasive-testing.md5 In Mbed TLS, we use black-box testing as much as possible: test the documented behavior of the prod…
9 This is a test strategy document, not a test plan. A description of exactly what is tested is out o…
30 Do not add test-specific interfaces if there's a practical way of doing it another way. All public …
34 In unit tests and in test programs, it's ok to include internal header files from `library/`. Do no…
36 …ch functions in `library/*.h` and include the corresponding header in the test code. If the functi…
38 If test code or test data depends on internal details of the library and not just on its documented…
41 > /* This test file is specific to the ITS implementation in PSA Crypto
48 > # This test assumes that PSA_MAX_KEY_BITS (currently 65536-8 bits = 8191 bytes
55 If the most practical way to test something is to add code to the product that is only useful for t…
57 * **Only use test-specific code when necessary.** Anything that can be tested through the documente…
[all …]
Dpsa-storage-format-testing.md7 …ne a test strategy for the key store that not only validates that it's possible to load a key that…
19 …ting test data under version V, and reading it back under version W. Done naively, this would requ…
23test cases under a version V of Mbed TLS, where the test case parameters include both the paramete…
25test case also loads the key and checks that it has the expected data and metadata. Import-and-sav…
27 If the test passes with version V, this means that the test data is consistent with what the implem…
37test cases used to exist. It can only be enforced through review of library changes. The review is…
39 …g a version of the storage format), then we should keep the corresponding test cases in load-only …
52 … trusted storage interface on top of C stdio. This document addresses the test strategy for [PSA I…
56 …d test cases for keys created with the current storage format version. When the storage format cha…
60 Objective: test that the key file name corresponds to the key identifier.
[all …]
Ddriver-interface-test-strategy.md1 # Mbed TLS driver interface test strategy
3 This document describes the test strategy for the driver interfaces in Mbed TLS. Mbed TLS has inter…
25 …e element driver interface. Note that a test case may cover multiple requirements; for example a “…
35 * Make at least one test that successfully registers the maximum number of drivers and fails to reg…
41 * Make at least one test with a key in a secure element that checks that the driver method is calle…
42 * Make at least one test with a key that is not in a secure element that checks that the driver met…
43 * Make at least one test with a key in a secure element with a driver that does not have the requis…
44 * Make at least one test with a key in a secure element with a driver that does not have the substr…
45 * At least one test should register multiple drivers with a key in each driver and check that the e…
46 * At least one test should register the same driver structure with multiple lifetime values and che…
[all …]
/mbedtls-latest/programs/
D.gitignore55 test/benchmark
56 test/cpp_dummy_build
57 test/cpp_dummy_build.cpp
58 test/dlopen
59 test/ecp-bench
60 test/metatest
61 test/query_compile_time_config
62 test/query_included_headers
63 test/selftest
64 test/ssl_cert_test
[all …]
/mbedtls-latest/tests/src/
Dhelpers.c65 static void mbedtls_test_set_result_internal(mbedtls_test_result_t result, const char *test, in mbedtls_test_set_result_internal() argument
72 mbedtls_test_info.test = test; in mbedtls_test_set_result_internal()
79 const char *test; in mbedtls_test_get_test() local
85 test = mbedtls_test_info.test; in mbedtls_test_get_test()
91 return test; in mbedtls_test_get_test()
379 static void mbedtls_test_fail_internal(const char *test, int line_no, const char *filename) in mbedtls_test_fail_internal() argument
388 mbedtls_test_set_result_internal(MBEDTLS_TEST_RESULT_FAILED, test, line_no, filename); in mbedtls_test_fail_internal()
392 void mbedtls_test_fail(const char *test, int line_no, const char *filename) in mbedtls_test_fail() argument
398 mbedtls_test_fail_internal(test, line_no, filename); in mbedtls_test_fail()
405 void mbedtls_test_skip(const char *test, int line_no, const char *filename) in mbedtls_test_skip() argument
[all …]
/mbedtls-latest/programs/test/
Dselftest.c373 const selftest_t *test; in main() local
526 for (test = selftests; test->name != NULL; test++) { in main()
527 if (!strcmp(*argp, test->name)) { in main()
528 if (test->function(v) != 0) { in main()
535 if (test->name == NULL) { in main()
542 for (test = selftests; test->name != NULL; test++) { in main()
546 if (!strcmp(*excluded, test->name)) { in main()
552 mbedtls_printf(" Skip: %s\n", test->name); in main()
557 if (test->function(v) != 0) { in main()
/mbedtls-latest/tests/scripts/
Dtest_zeroize.gdb8 # Run a test using the debugger to check that the mbedtls_platform_zeroize()
10 # so, the script loads the test program at programs/test/zeroize.c and sets a
15 # The mbedtls_platform_zeroize() test is debugger driven because there does not
27 # inserting a test after a call to mbedtls_platform_zeroize() to check whether
32 # Note: This test requires that the test program is compiled with -g3.
36 file ./programs/test/zeroize
41 set args ./programs/test/zeroize.c
Dtest_psa_compliance.py99 test = -1
113 test = int(test_num)
116 unexpected_successes.remove(test)
117 expected_failures.append(test)
120 unexpected_failures.append(test)
122 elif test in unexpected_successes:
/mbedtls-latest/tests/include/test/
Dhelpers.h73 const char *test; member
211 void mbedtls_test_fail(const char *test, int line_no, const char *filename);
224 void mbedtls_test_skip(const char *test, int line_no, const char *filename);
279 int mbedtls_test_equal(const char *test, int line_no, const char *filename,
300 int mbedtls_test_le_u(const char *test, int line_no, const char *filename,
321 int mbedtls_test_le_s(const char *test, int line_no, const char *filename,
/mbedtls-latest/programs/fuzz/
DREADME.md35 Finally, you can run the targets like `./test/fuzz/fuzz_client`.
51 …m one against the other with `reproducible` option turned on while capturing traffic into test.pcap
52 … for instance with tshark : `tshark -Tfields -e tcp.dstport -e tcp.payload -r test.pcap > test.txt`
53 …hon script to output either client or server corpus file like `python dummy.py test.txt > test.cor`
54 * Finally, you can add the options by appending the last bytes to the file test.cor
/mbedtls-latest/tests/
DDescriptions.txt3 using 'make check' (Unix make) or 'make test' (Cmake), include test cases
4 (reference test vectors, sanity checks, malformed input for parsing
8 The 'programs/test/selftest' program runs the 'XXX_self_test()' functions
10 test suite, but some slower ones are only included here.

1234567