Home
last modified time | relevance | path

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

12345

/mbedtls-development/tests/suites/
A 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]
133 ECDSA deterministic test vector rfc 6979 p224 sha1 [#1]
153 ECDSA deterministic test vector rfc 6979 p224 sha1 [#2]
173 ECDSA deterministic test vector rfc 6979 p256 sha1 [#1]
193 ECDSA deterministic test vector rfc 6979 p256 sha1 [#2]
[all …]
A 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)
13 SE key importing mock test
16 SE key importing mock test: max key bits
28 SE key exporting mock test
34 SE public key exporting mock test
40 SE key generating mock test
49 SE signing mock test
52 SE signing mock test: sign failed
[all …]
A Dtest_suite_cipher.ccm.data1 AES-128-CCM test vector NIST #1 (P=0, N=7, A=0, T=4)
385 Camellia-CCM test vector RFC 5528 #1
389 Camellia-CCM test vector RFC 5528 #2
393 Camellia-CCM test vector RFC 5528 #3
397 Camellia-CCM test vector RFC 5528 #4
401 Camellia-CCM test vector RFC 5528 #5
405 Camellia-CCM test vector RFC 5528 #6
409 Camellia-CCM test vector RFC 5528 #7
413 Camellia-CCM test vector RFC 5528 #8
417 Camellia-CCM test vector RFC 5528 #9
[all …]
A 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 …]
A Dtest_suite_mpi.data4 Base test mpi_read_write_string #1
10 Base test mpi_read_write_string #2
124 Base test mbedtls_mpi_lsb #1
127 Base test mbedtls_mpi_lsb #2
130 Base test mbedtls_mpi_lsb #3
133 Base test mbedtls_mpi_lsb #4
136 Base test mbedtls_mpi_bitlen #1
139 Base test mbedtls_mpi_bitlen #2
1314 Base test GCD #1
1317 Base test GCD #2
[all …]
A Dtest_suite_psa_crypto_se_driver_hal.data66 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
93 Key import smoke test: ARIA-GCM
[all …]
A Dtest_suite_pk.data47 RSA verify test vector #1 (good)
51 RSA verify test vector #2 (bad)
55 ECDSA verify test vector #1 (good)
59 ECDSA verify test vector #2 (bad)
63 EC(DSA) verify test vector #1 (good)
67 EC(DSA) verify test vector #2 (bad)
71 EC(DSA) verify test vector: good, bitlen(r) = 256
75 EC(DSA) verify test vector: good, bitlen(r) = 255
139 RSA encrypt test vector
143 RSA decrypt test vector #1
[all …]
A Dtest_suite_psa_crypto_storage_format.misc.data1 # The following two manually crafted test cases are redundant with
2 # systematically generated test cases, but useful to have as an anchor when
3 # debugging changes to the test code or to the test case generation.
A Dhelpers.function5 #include <test/helpers.h>
6 #include <test/macros.h>
7 #include <test/random.h>
8 #include <test/psa_crypto_helpers.h>
69 #define DISPATCH_INVALID_TEST_DATA -4 /* Invalid test parameter type.
98 * If any slots are in use, mark the current test as failed.
A Dtest_suite_x509parse.data396 mbedtls_x509_time_is_past:"data_files/test-ca.crt":"valid_from":1
400 mbedtls_x509_time_is_past:"data_files/test-ca.crt":"valid_to":0
420 mbedtls_x509_time_is_future:"data_files/test-ca2.crt":"valid_from":0
424 mbedtls_x509_time_is_future:"data_files/test-ca2.crt":"valid_to":1
632 x509_verify:"data_files/test-ca.crt":"data_files/test-ca.crt":"data_files/crl.pem":"NULL":0:0:"comp…
636 x509_verify:"data_files/test-ca2.crt":"data_files/test-ca2.crt":"data_files/crl-ec-sha256.pem":"NUL…
1507 # namely the v3 extensions. However, the tag the test exercises is a NULL tag,
2233 mbedtls_x509_crt_verify_chain:"data_files/server7.crt data_files/test-int-ca.crt":"data_files/test-…
2241 mbedtls_x509_crt_verify_chain:"data_files/server7.crt data_files/test-int-ca.crt":"data_files/test-…
2717 x509_verify_restart:"data_files/server5.crt":"data_files/test-ca2.crt":0:0:0:0:0
[all …]
A Dtest_suite_x509write.data55 x509_crt_check:"data_files/server1.key":"":"C=NL,O=PolarSSL,CN=PolarSSL Server 1":"data_files/test-…
59 x509_crt_check:"data_files/server1.key":"":"C=NL,O=PolarSSL,CN=PolarSSL Server 1":"data_files/test-…
63 x509_crt_check:"data_files/server1.key":"":"C=NL,O=PolarSSL,CN=PolarSSL Server 1":"data_files/test-…
67 x509_crt_check:"data_files/server1.key":"":"C=NL,O=PolarSSL,CN=PolarSSL Server 1":"data_files/test-…
71 x509_crt_check:"data_files/server1.key":"":"C=NL,O=PolarSSL,CN=PolarSSL Server 1":"data_files/test-…
75 x509_crt_check:"data_files/server1.key":"":"C=NL,O=PolarSSL,CN=PolarSSL Server 1":"data_files/test-…
79 x509_crt_check:"data_files/server1.key":"":"C=NL,O=PolarSSL,CN=PolarSSL Server 1":"data_files/test-…
83 x509_crt_check:"data_files/server1.key":"":"C=NL,O=PolarSSL,CN=PolarSSL Server 1":"data_files/test-…
87 x509_crt_check:"data_files/server1.key":"":"C=NL,O=PolarSSL,CN=PolarSSL Server 1":"data_files/test-…
91 x509_crt_check:"data_files/server1.key":"":"C=NL,O=PolarSSL,CN=PolarSSL Server 1":"data_files/test-…
/mbedtls-development/docs/architecture/testing/
A 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
13 …test case has a description which succinctly describes for a human audience what the test does. Th…
21 … lot of test cases with longer descriptions, but they should be avoided. At least please make sure…
31 #### SSL test case descriptions
33 Each test case in `ssl-opt.sh` has a description which succinctly describes for a human audience wh…
35 The same rules and guidelines apply as for [unit test descriptions](#unit-test-descriptions). In ad…
43 Unit tests and `ssl-opt.sh` record the outcome of each test case in a **test outcome file**. This f…
45 If you run `all.sh --outcome-file test-outcome.csv`, this collects the outcome of all the test case…
[all …]
A Dinvasive-testing.md9 This is a test strategy document, not a test plan. A description of exactly what is tested is out o…
73 In unit test code that needs to modify the internal behavior:
75 * The test function (or the whole test file) must depend on `MBEDTLS_TEST_HOOKS`.
284 Goal: test the absence of memory leaks.
288 …test jobs with a memory leak detector, each test function or test program must clean up after itse…
292 Solution: TODO. We don't test this at all at this point.
308 Goal: test that no stray files are left over in the key store after a test that succeeded.
324 See the [secure element driver interface test strategy](driver-interface-test-strategy.html) for mo…
328 Goal: test the robustness against corrupted storage.
334 Goal: test the robustness against read errors.
[all …]
A 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…
23 …test cases under a version V of Mbed TLS, where the test case parameters include both the paramete…
25 …test 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…
60 Objective: test that the key file name corresponds to the key identifier.
66 Objective: test the format of the key file: which field goes where and how big it is.
70 ### Enumeration of test cases for keys
74 …validate that each `PSA_xxx` constant that is stored in a key is covered by at least one test case:
83 Method: Each test case creates a key with `psa_import_key`, purges it from memory, then reads it ba…
[all …]
A Ddriver-interface-test-strategy.md1 # Mbed Crypto driver interface test strategy
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…
42 * Make at least one test with a key that is not in a secure element that checks that the driver met…
46 * At least one test should register the same driver structure with multiple lifetime values and che…
48 … that provides the MAC methods must provide all or none). In those cases, test with all of them nu…
65 * Unexpected errors. At least test that if the driver returns `PSA_ERROR_GENERIC_ERROR`, this is pr…
102 * Run the full driver validation test suite (which does not yet exist).
103 * Run at least one test application (e.g. the Mbed OS TLS example).
113 * Run the full driver validation test suite (which does not yet exist).
[all …]
/mbedtls-development/programs/
A D.gitignore10 /test/query_config.c
57 test/benchmark
58 test/cpp_dummy_build
59 test/cpp_dummy_build.cpp
60 test/ecp-bench
61 test/query_compile_time_config
62 test/selftest
63 test/ssl_cert_test
64 test/udp_proxy
65 test/zeroize
/mbedtls-development/tests/data_files/
A DReadme-x509.txt9 test-ca-sha1.crt and test-ca-sha256.crt use the same key, signed with
13 variants used to test the keyUsage extension
14 The files test-ca_cat12 and test-ca_cat21 contain them concatenated both ways.
18 uses RSA-4096, signed by test-ca2
30 - test-ca-v1.crt: v1 "CA", signs
41 - issuing CA: 1 -> test-ca.crt
42 2 -> test-ca2.crt
43 I1 -> test-int-ca.crt
44 I2 -> test-int-ca2.crt
45 I3 -> test-int-ca3.crt
[all …]
A Dtest-ca.server1.opensslconf2 default_ca = test-ca
4 [ test-ca ]
5 certificate = test-ca.crt
6 private_key = test-ca.key
7 serial = test-ca.server1.serial
12 database = ./test-ca.server1.db
A Dtest-ca.server1.future-crl.opensslconf2 default_ca = test-ca
4 [ test-ca ]
5 certificate = test-ca.crt
6 private_key = test-ca.key
7 serial = test-ca.server1.serial
12 database = ./test-ca.server1.future-crl.db
/mbedtls-development/programs/test/
A Dselftest.c340 const selftest_t *test; in main() local
402 for( test = selftests; test->name != NULL; test++ ) in main()
404 if( !strcmp( *argp, test->name ) ) in main()
406 if( test->function( v ) != 0 ) in main()
414 if( test->name == NULL ) in main()
424 for( test = selftests; test->name != NULL; test++ ) in main()
431 if( !strcmp( *excluded, test->name ) ) in main()
437 mbedtls_printf( " Skip: %s\n", test->name ); in main()
441 if( test->function( v ) != 0 ) in main()
/mbedtls-development/tests/src/
A Dhelpers.c64 void mbedtls_test_fail( const char *test, int line_no, const char* filename ) in mbedtls_test_fail() argument
73 mbedtls_test_info.test = test; in mbedtls_test_fail()
78 void mbedtls_test_skip( const char *test, int line_no, const char* filename ) in mbedtls_test_skip() argument
81 mbedtls_test_info.test = test; in mbedtls_test_skip()
95 mbedtls_test_info.test = 0; in mbedtls_test_info_reset()
102 int mbedtls_test_equal( const char *test, int line_no, const char* filename, in mbedtls_test_equal() argument
113 mbedtls_test_fail( test, line_no, filename ); in mbedtls_test_equal()
/mbedtls-development/tests/
A 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.
/mbedtls-development/tests/scripts/
A Dtest_zeroize.gdb20 # Run a test using the debugger to check that the mbedtls_platform_zeroize()
22 # so, the script loads the test program at programs/test/zeroize.c and sets a
27 # The mbedtls_platform_zeroize() test is debugger driven because there does not
39 # inserting a test after a call to mbedtls_platform_zeroize() to check whether
44 # Note: This test requires that the test program is compiled with -g3.
48 file ./programs/test/zeroize
53 set args ./programs/test/zeroize.c
/mbedtls-development/tests/include/test/
A Dhelpers.h72 const char *test; member
104 void mbedtls_test_fail( const char *test, int line_no, const char* filename );
117 void mbedtls_test_skip( const char *test, int line_no, const char* filename );
154 int mbedtls_test_equal( const char *test, int line_no, const char* filename,
/mbedtls-development/programs/fuzz/
A DREADME.md35 Finally, you can run the targets like `./test/fuzz/fuzz_client`.
51 …em one against the other with `reproducible` option turned on while capturing trafic 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

Completed in 47 milliseconds

12345