test (reference) in projects: mbedtls-3.4.0

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5

/mbedtls-3.4.0/tests/suites/
D	test_suite_cipher.ccm.data	1 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 …]
D	test_suite_gcm.camellia.data	1 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 …]
D	test_suite_lmots.data	1 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 …]
D	test_suite_psa_crypto_se_driver_hal_mocks.data	`1 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 …]`
D	test_suite_lms.data	1 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 …]
D	test_suite_bignum.misc.data	4 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 …]
D	test_suite_psa_crypto_se_driver_hal.data	`4 # 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 …]`
D	test_suite_ecdsa.data	93 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 …]
D	test_suite_x509write.data	63 …test-ca.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"1":"20190210144406":"2029021014… 67 …test-ca.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"1":"19700210144406":"2029021014… 71 …test-ca.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"1":"20190210144406":"2050021014… 75 …test-ca.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"1":"19700210144406":"2050021014… 79 …test-ca.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"1":"20500210144406":"2059021014… 83 …test-ca.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"1":"20190210144406":"2029021014… 87 …test-ca.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"1":"20110212144406":"2021021214… 91 …test-ca.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"1":"20110212144406":"2021021214… 95 …test-ca.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"1":"20190210144406":"2029021014… 99 …test-ca.key":"PolarSSLTest":"C=NL,O=PolarSSL,CN=PolarSSL Test CA":"1":"20190210144406":"2029021014… [all …]
D	test_suite_psa_crypto_storage_format.misc.data	`1 # 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.`
/mbedtls-3.4.0/docs/architecture/testing/
D	test-framework.md	1 # 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… 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 …]
D	invasive-testing.md	5 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 …]
D	psa-storage-format-testing.md	7 …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… 37 …test 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 …]
D	driver-interface-test-strategy.md	1 # Mbed Crypto driver interface test strategy 3 This document describes the test strategy for the driver interfaces in Mbed Crypto. Mbed Crypto has… 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-3.4.0/programs/
D	.gitignore	`10 /test/query_config.c 61 test/benchmark 62 test/cpp_dummy_build 63 test/cpp_dummy_build.cpp 64 test/dlopen 65 test/ecp-bench 66 test/query_compile_time_config 67 test/query_included_headers 68 test/selftest 69 test/ssl_cert_test [all …]`
/mbedtls-3.4.0/tests/data_files/
D	Readme-x509.txt	7 - test-ca.crt aka "C=NL, O=PolarSSL, CN=PolarSSL Test CA" 9 test-ca-sha1.crt and test-ca-sha256.crt use the same key, signed with 11 - test-ca2*.crt aka "C=NL, O=PolarSSL, CN=Polarssl Test EC CA" 13 variants used to test the keyUsage extension 14 The files test-ca_cat12 and test-ca_cat21 contain them concatenated both ways. 17 - test-int-ca.crt "C=NL, O=PolarSSL, CN=PolarSSL Test Intermediate CA" 18 uses RSA-4096, signed by test-ca2 19 - test-int-ca-exp.crt is a copy that is expired 20 - test-int-ca2.crt "C=NL, O=PolarSSL, CN=PolarSSL Test Intermediate EC CA" 21 uses an EC key with NIST P-384, signed by test-ca [all …]
D	test-ca.server1.opensslconf	`2 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`
D	test-ca.server1.future-crl.opensslconf	`2 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-3.4.0/programs/test/
D	selftest.c	`326 const selftest_t test; in main() local 460 for( test = selftests; test->name != NULL; test++ ) in main() 462 if( !strcmp( argp, test->name ) ) in main() 464 if( test->function( v ) != 0 ) in main() 472 if( test->name == NULL ) in main() 482 for( test = selftests; test->name != NULL; test++ ) in main() 489 if( !strcmp( *excluded, test->name ) ) in main() 495 mbedtls_printf( " Skip: %s\n", test->name ); in main() 499 if( test->function( v ) != 0 ) in main()`
/mbedtls-3.4.0/tests/src/
D	helpers.c	65 void mbedtls_test_fail( const char test, int line_no, const char filename ) in mbedtls_test_fail() argument 74 mbedtls_test_info.test = test; in mbedtls_test_fail() 79 void mbedtls_test_skip( const char test, int line_no, const char filename ) in mbedtls_test_skip() argument 82 mbedtls_test_info.test = test; in mbedtls_test_skip() 100 mbedtls_test_info.test = 0; in mbedtls_test_info_reset() 110 int mbedtls_test_equal( const char test, int line_no, const char filename, in mbedtls_test_equal() argument 125 mbedtls_test_fail( test, line_no, filename ); in mbedtls_test_equal() 137 int mbedtls_test_le_u( const char test, int line_no, const char filename, in mbedtls_test_le_u() argument 152 mbedtls_test_fail( test, line_no, filename ); in mbedtls_test_le_u() 164 int mbedtls_test_le_s( const char test, int line_no, const char filename, in mbedtls_test_le_s() argument [all …]
/mbedtls-3.4.0/tests/include/test/
D	helpers.h	`66 const char test; member 98 void mbedtls_test_fail( const char test, int line_no, const char* filename ); 111 void mbedtls_test_skip( const char test, int line_no, const char filename ); 148 int mbedtls_test_equal( const char test, int line_no, const char filename, 169 int mbedtls_test_le_u( const char test, int line_no, const char filename, 190 int mbedtls_test_le_s( const char test, int line_no, const char filename,`
/mbedtls-3.4.0/tests/scripts/
D	test_psa_compliance.py	`96 test = -1 107 test = int(test_num) 110 unexpected_successes.remove(test) 111 expected_failures.append(test) 114 unexpected_failures.append(test) 116 elif test in unexpected_successes:`
D	test_zeroize.gdb	`20 # 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-3.4.0/tests/
D	Descriptions.txt	`3 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-3.4.0/programs/fuzz/
D	README.md	35 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

12 3 4 5

TraceRecorderSource-2.7.6
TraceRecorderSource-3.4.0
Zephyr-Core-2.7.6
Zephyr-Core-3.4.0
Zephyr-Core-3.5.0
Zephyr-Core-3.6.0
Zephyr-Core-3.7.0
acpica-3.5.0
acpica-3.6.0
acpica-3.7.0
babblesim_base-3.4.0
babblesim_base-3.6.0-3.5.0
babblesim_base-3.7.0
babblesim_ext_2G4_channel_NtNcable-3.7.0-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_channel_multiatt-3.4.0
babblesim_ext_2G4_channel_multiatt-3.7.0-3.6.0-3.5.0
babblesim_ext_2G4_device_WLAN_actmod-3.7.0-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_device_burst_interferer-3.7.0-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_device_playback-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_device_playback-3.7.0
babblesim_ext_2G4_libPhyComv1-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_libPhyComv1-3.7.0
babblesim_ext_2G4_modem_BLE_simple-3.4.0
babblesim_ext_2G4_modem_BLE_simple-3.6.0-3.5.0
babblesim_ext_2G4_modem_BLE_simple-3.7.0
babblesim_ext_2G4_modem_magic-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_modem_magic-3.7.0
babblesim_ext_2G4_phy_v1-3.4.0
babblesim_ext_2G4_phy_v1-3.6.0-3.5.0
babblesim_ext_2G4_phy_v1-3.7.0
babblesim_ext_libCryptov1-3.7.0-3.6.0-3.5.0-3.4.0
bsim-3.4.0
bsim-3.6.0-3.5.0
bsim-3.7.0
canopennode-2.7.6
canopennode-3.5.0-3.4.0
chre-3.4.0
civetweb-2.7.6
cmsis-2.7.6
cmsis-3.4.0
cmsis-3.5.0
cmsis-3.7.0-3.6.0
cmsis-dsp-3.5.0
cmsis-dsp-3.7.0-3.6.0
cmsis-nn-3.6.0-3.5.0
cmsis-nn-3.7.0
edtt-2.7.6
edtt-3.6.0-3.5.0-3.4.0
edtt-3.7.0
fatfs-2.7.6
fatfs-3.7.0-3.6.0-3.5.0-3.4.0
hal_adi-3.7.0
hal_altera-2.7.6
hal_altera-3.6.0-3.5.0-3.4.0
hal_altera-3.7.0
hal_ambiq-3.5.0
hal_ambiq-3.6.0
hal_ambiq-3.7.0
hal_atmel-2.7.6
hal_atmel-3.5.0-3.4.0
hal_atmel-3.6.0
hal_atmel-3.7.0
hal_cypress-2.7.6
hal_espressif-2.7.6
hal_espressif-3.4.0
hal_espressif-3.5.0
hal_espressif-3.6.0
hal_espressif-3.7.0
hal_ethos_u-3.6.0-3.5.0-3.4.0
hal_ethos_u-3.7.0
hal_gigadevice-3.7.0-3.6.0-3.5.0-3.4.0
hal_infineon-2.7.6
hal_infineon-3.4.0
hal_infineon-3.5.0
hal_infineon-3.6.0
hal_infineon-3.7.0
hal_intel-3.5.0
hal_intel-3.6.0
hal_intel-3.7.0
hal_microchip-2.7.6
hal_microchip-3.6.0-3.5.0-3.4.0
hal_microchip-3.7.0
hal_nordic-2.7.6
hal_nordic-3.4.0
hal_nordic-3.5.0
hal_nordic-3.6.0
hal_nordic-3.7.0
hal_nuvoton-2.7.6
hal_nuvoton-3.4.0
hal_nuvoton-3.5.0
hal_nuvoton-3.6.0
hal_nuvoton-3.7.0
hal_nxp-2.7.6
hal_nxp-3.4.0
hal_nxp-3.5.0
hal_nxp-3.6.0
hal_nxp-3.7.0
hal_openisa-2.7.6
hal_openisa-3.5.0-3.4.0
hal_openisa-3.7.0-3.6.0
hal_quicklogic-3.6.0-3.5.0-3.4.0-2.7.6
hal_quicklogic-3.7.0
hal_renesas-3.4.0
hal_renesas-3.5.0
hal_renesas-3.6.0
hal_renesas-3.7.0
hal_rpi_pico-3.4.0
hal_rpi_pico-3.7.0-3.6.0-3.5.0
hal_silabs-2.7.6
hal_silabs-3.4.0
hal_silabs-3.5.0
hal_silabs-3.6.0
hal_silabs-3.7.0
hal_st-2.7.6
hal_st-3.4.0
hal_st-3.5.0
hal_st-3.6.0
hal_st-3.7.0
hal_stm32-2.7.6
hal_stm32-3.4.0
hal_stm32-3.5.0
hal_stm32-3.6.0
hal_stm32-3.7.0
hal_telink-2.7.6
hal_telink-3.6.0-3.5.0-3.4.0
hal_telink-3.7.0
hal_ti-2.7.6
hal_ti-3.4.0
hal_ti-3.7.0-3.6.0-3.5.0
hal_wurthelektronik-3.5.0-3.4.0
hal_wurthelektronik-3.7.0-3.6.0
hal_xtensa-2.7.6
hal_xtensa-3.4.0
hal_xtensa-3.5.0
hal_xtensa-3.6.0
hal_xtensa-3.7.0
hostap-3.6.0
hostap-3.7.0
liblc3-3.5.0-3.4.0
liblc3-3.7.0-3.6.0
libmetal-2.7.6
libmetal-3.5.0-3.4.0
libmetal-3.6.0
libmetal-3.7.0
littlefs-2.7.6
littlefs-3.5.0-3.4.0
littlefs-3.7.0-3.6.0
loramac-node-2.7.6
loramac-node-3.4.0
loramac-node-3.6.0-3.5.0
loramac-node-3.7.0
lvgl-2.7.6
lvgl-3.4.0
lvgl-3.5.0
lvgl-3.6.0
lvgl-3.7.0
lz4-3.4.0-2.7.6
mbedtls-2.7.6
mbedtls-3.4.0
mbedtls-3.5.0
mbedtls-3.6.0
mbedtls-3.7.0
mcuboot-2.7.6
mcuboot-3.4.0
mcuboot-3.5.0
mcuboot-3.6.0
mcuboot-3.7.0
mcumgr-2.7.6
mipi-sys-t-2.7.6
mipi-sys-t-3.4.0
mipi-sys-t-3.6.0-3.5.0
mipi-sys-t-3.7.0
nanopb-2.7.6
nanopb-3.4.0
net-tools-2.7.6
net-tools-3.4.0
net-tools-3.5.0
net-tools-3.6.0
net-tools-3.7.0
nrf_hw_models-2.7.6
nrf_hw_models-3.4.0
nrf_hw_models-3.5.0
nrf_hw_models-3.6.0
nrf_hw_models-3.7.0
open-amp-2.7.6
open-amp-3.4.0
open-amp-3.5.0
open-amp-3.6.0
open-amp-3.7.0
openthread-2.7.6
openthread-3.4.0
openthread-3.5.0
openthread-3.6.0
openthread-3.7.0
percepio-3.5.0
percepio-3.6.0
percepio-3.7.0
picolibc-3.5.0-3.4.0
picolibc-3.7.0-3.6.0
psa-arch-tests-3.4.0
segger-2.7.6
segger-3.4.0
segger-3.6.0-3.5.0
segger-3.7.0
sof-2.7.6
sof-3.4.0
tf-m-tests-3.4.0
tflite-micro-3.4.0-2.7.6
thrift-3.4.0
tinycbor-2.7.6
tinycrypt-3.6.0-3.5.0-3.4.0-2.7.6
tinycrypt-3.7.0
trusted-firmware-a-3.4.0
trusted-firmware-a-3.6.0-3.5.0
trusted-firmware-a-3.7.0
trusted-firmware-m-3.4.0
trusted-firmware-m-3.5.0
trusted-firmware-m-3.6.0
trusted-firmware-m-3.7.0
uoscore-uedhoc-3.4.0
uoscore-uedhoc-3.5.0
uoscore-uedhoc-3.6.0
uoscore-uedhoc-3.7.0
zcbor-3.5.0-3.4.0
zcbor-3.6.0
zcbor-3.7.0
zscilib-3.4.0