| /mbedtls-development/programs/psa/ |
| A D | key_ladder_demo.sh | 23 run () { function
35 run "Generate a master key." \
41 run "Derive a key and wrap some data with it." \
46 run "Derive the same key again and unwrap the data." \
49 run "Compare the unwrapped data with the original input." \
53 ! run "Derive a different key and attempt to unwrap the data. This must fail." \
57 run "Save the first step of the key ladder, then load it as a master key and construct the rest of …
60 run "Check that we get the same key by unwrapping data made by the other key." \
|
| A D | key_ladder_demo.c | 528 static psa_status_t run( enum program_mode mode, in run() function
692 status = run( mode, key_file_name, in main()
|
| /mbedtls-development/programs/fuzz/ |
| A D | README.md | 12 How to run?
15 To run the fuzz targets like oss-fuzz:
24 And you can run any of the fuzz targets like `fuzz_client`.
26 To run the fuzz targets without oss-fuzz, you first need to install one libFuzzingEngine (libFuzzer…
35 Finally, you can run the targets like `./test/fuzz/fuzz_client`.
|
| /mbedtls-development/scripts/ |
| A D | ecp_comb_table.py | 184 p = subprocess.run(args=args, check=False)
187 p = subprocess.run(args=[binname], check=False, env={
|
| /mbedtls-development/ChangeLog.d/ |
| A D | issue5065.txt | 2 * Fix compile-time or run-time errors in PSA
|
| A D | session_export_private.txt | 4 oversight during the run-up to the release of Mbed TLS 3.0.
|
| /mbedtls-development/tests/scripts/ |
| A D | check_names.py | 589 subprocess.run(
598 subprocess.run(
603 subprocess.run(
619 subprocess.run(
657 nm_output += subprocess.run(
|
| A D | docker_env.sh | 88 ${DOCKER} container run -it --rm \
|
| A D | test_config_script.py | 92 help_text = subprocess.run([options.script, '--help'],
|
| A D | basic-build-test.sh | 108 perl scripts/run-test-suites.pl -v 2 |tee unit-test-$TEST_OUTPUT
|
| A D | test_zeroize.gdb | 54 run
|
| A D | all.sh | 223 By default, run all tests. With one or more COMPONENT, run only those.
251 files. Do not run any components unless they are
253 --error-test Error test mode: run a failing function in addition
268 -s|--seed Integer seed value to use for this test run.
|
| /mbedtls-development/ |
| A D | README.md | 50 * Perl to run the tests, and to generate some source files in the development branch.
72 * On Unix/POSIX systems, run `tests/scripts/check-generated-files.sh -u` to generate all the config…
73 * On Windows, run `scripts\make_generated_files.bat` to generate all the configuration-independent …
85 In order to run the tests, enter:
89 The tests need Python to be built and Perl to be run. If you don't have one of them installed, you …
93 You'll still be able to run a much smaller set of tests with:
103 Depending on your platform, you might run into some issues. Please check the Makefiles in `library/…
115 In order to run the tests, enter:
123 If you disabled the test suites, but kept the programs enabled, you can still run a much smaller se…
264 …on, which allows substituting alternative implementations at build time or run time, for example, …
|
| /mbedtls-development/tests/git-scripts/ |
| A D | README.md | 3 git has a way to run scripts, which are invoked by specific git commands.
|
| /mbedtls-development/tests/suites/ |
| A D | test_suite_entropy.function | 475 // Do an entropy run
483 // First run for updating write_seed
498 // Second run for actual entropy (triggers mbedtls_entropy_update_nv_seed)
|
| A D | test_suite_net.function | 100 * test will run if it can.
|
| A D | test_suite_psa_crypto_persistent_key.data | 31 # Not specific to files, but only run this test in an environment where the maximum size could be r…
|
| A D | test_suite_hmac_drbg.function | 206 /* Reset context for second run */
|
| /mbedtls-development/scripts/data_files/ |
| A D | vs6-main-template.dsp | 9 !MESSAGE use the Export Makefile command and run
|
| A D | vs6-app-template.dsp | 9 !MESSAGE use the Export Makefile command and run
|
| /mbedtls-development/tests/ |
| A D | Makefile | 198 perl scripts/run-test-suites.pl $(TEST_FLAGS) --skip=$(SKIP_TEST_SUITES)
|
| /mbedtls-development/docs/architecture/testing/ |
| A D | test-framework.md | 45 If you run `all.sh --outcome-file test-outcome.csv`, this collects the outcome of all the test case…
|
| /mbedtls-development/tests/docker/bionic/ |
| A D | Dockerfile | 5 # Defines a Docker container suitable to build and run all tests (all.sh),
|
| /mbedtls-development/doxygen/ |
| A D | mbedtls.doxyfile | 140 # If left blank the directory from which doxygen is run is used as the
590 # that represents doxygen's defaults, run doxygen with the -l option.
697 # run.
1042 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
1118 # If non-empty doxygen will try to run qhelpgenerator on the generated
1180 # when you change the font size after a successful doxygen run you need
1657 # doxygen is run, you must also specify the path to the tagfile here.
1702 # command. Doxygen will then run the mscgen tool (see
1724 # allowed to run in parallel. When set to 0 (the default) doxygen will
1815 # the time of a run. So in most cases it will be better to enable caller
[all …]
|
| /mbedtls-development/docs/ |
| A D | getting_started.md | 48 * Perl to run the tests.
50 If you have a C compiler such as GCC or Clang, just run `make` in the top-level directory to build …
58 To run the unit tests on the host machine, run `make test` from the top-level directory. If you are…
|