Home
last modified time | relevance | path

Searched refs:code (Results 1 – 25 of 62) sorted by relevance

123

/mbedtls-development/library/
A Dmps_error.h51 #define MBEDTLS_MPS_MAKE_ERROR(code) \ argument
52 ( -( MBEDTLS_MPS_ERR_BASE | (code) ) )
69 #define MBEDTLS_MPS_READER_MAKE_ERROR(code) \ argument
70 ( -( MBEDTLS_MPS_READER_ERR_BASE | (code) ) )
/mbedtls-development/tests/scripts/
A Dgenerate_test_code.py515 if code.find('exit:') == -1:
516 split_code = code.rsplit('}', 1)
518 code = """exit:
539 code = ''
559 code += line
561 code += line
567 code = code.replace(name, 'test_' + name, 1)
576 code += line
581 code = line_directive + code
582 code = generate_function_code(name, code, local_vars, args_dispatch,
[all …]
A Dtest_generate_test_code.py215 self.assertEqual(code, expected)
223 code = gen_function_wrapper('test_a',
232 self.assertEqual(code, expected)
240 code = gen_function_wrapper('test_a', '', ())
249 self.assertEqual(code, expected)
270 self.assertEqual(code, expected)
277 code = gen_dispatch('test_a', [])
281 self.assertEqual(code, expected)
624 self.assertEqual(code, expected)
668 self.assertEqual(code, expected)
[all …]
A Dtest_zeroize.gdb31 # "unnecessary" assignments as part of redundant code elimination. To identify
32 # such code, the compilar will create some form dependency graph between
34 # data structure to remove redundant code that does not have an impact on the
/mbedtls-development/programs/ssl/
A Dssl_mail_client.c254 char code[4]; in write_ssl_and_get_response() local
292 code[ idx++ ] = data[i]; in write_ssl_and_get_response()
296 if( idx == 4 && code[0] >= '0' && code[0] <= '9' && code[3] == ' ' ) in write_ssl_and_get_response()
298 code[3] = '\0'; in write_ssl_and_get_response()
299 return atoi( code ); in write_ssl_and_get_response()
312 char code[4]; in write_and_get_response() local
342 code[ idx++ ] = data[i]; in write_and_get_response()
346 if( idx == 4 && code[0] >= '0' && code[0] <= '9' && code[3] == ' ' ) in write_and_get_response()
348 code[3] = '\0'; in write_and_get_response()
349 return atoi( code ); in write_and_get_response()
/mbedtls-development/docs/architecture/testing/
A Dinvasive-testing.md38 If test code or test data depends on internal details of the library and not just on its documented…
58 * **Test-specific code must be guarded by `#if defined(MBEDTLS_TEST_HOOKS)`**. Do not create fine-g…
65 …ive code for test purposes. That is, library code calls `mbedtls_foo()`, and there is a mechanism …
73 In unit test code that needs to modify the internal behavior:
203 | Effacement | ++ Zero impact on the code |
217 | Portability | ++ It's just C code so it works everywhere |
219 …| + Test interfaces impact the product source code, but at least they're clearly marked as such in…
227 * **Minimize the impact on code**.<br>
228 …ve test-specific conditional compilation littered through the code, as that makes the code hard to…
241 | Effacement | ++ Zero impact on the code |
[all …]
/mbedtls-development/tests/suites/
A Dmain_test.function12 * Main code file : $test_main_file
13 * Platform code file : $test_platform_file
28 /* Test code may use deprecated identifiers only if the preprocessor symbol
38 /* Common helper code */
57 /* Test dispatch code */
64 * Identifiers and evaluation code is generated by script:
97 * Identifiers and check code is generated by script:
227 /* Main Test code */
236 * \return Exit code.
A Dtest_suite_error.function11 void error_strerror( int code, char * result_str )
17 mbedtls_strerror( code, buf, 500 );
A Dtest_suite_net.function31 * \return \c 0 on succes, a negative error code on error.
78 * descriptor greater or equal to FD_SETSIZE. This code is specific to
99 * might do); but we don't do such things in our test code, so the unit
121 * it may still happen to return the expected failure code, but if this
122 * is problematic on the particular platform where the code is running,
A Dtest_suite_psa_crypto_storage_format.misc.data3 # debugging changes to the test code or to the test case generation.
/mbedtls-development/docs/proposed/
A Dpsa-driver-integration-guide.md8 …r notice, we do not guarantee backward compatibility with existing driver code when `MBEDTLS_PSA_C…
12 The PSA cryptography driver interface provides a way to build Mbed TLS with additional code that im…
16 … **driver description files** in JSON format and some code to include in the build. The driver cod…
43 <!-- TODO: what if the driver is provided as C source code? -->
A Dpsa-conditional-inclusion-c.md32 …bly configured Mbed TLS build must not include the corresponding software code (unless a software …
73 * In Mbed TLS test code.
74 * In Mbed TLS library code using `MBEDTLS_USE_PSA_CRYPTO`, for example in TLS to determine which ci…
97 …code is usually not specialized for any particular group, so reducing the number of available grou…
116 … outputs of the transpilation of a driver description, alongside the glue code for calling the dri…
134 …code that uses these parts. This includes structure definitions in `psa/crypto_struct.h`, size cal…
145 * (D) indicates a symbol that is deduced from other symbols by code that ships with Mbed TLS.
158 …DTLS_PSA_BUILTIN_xxx` symbols should not be visible to application code or driver code, since they…
172 ### Structure of PSA Crypto library code
178 #### Conditional inclusion of mechanism-specific code argument
[all …]
/mbedtls-development/scripts/data_files/
A Derror.fmt46 /* Extract the high-level part from the error code. */
69 /* Extract the low-level part from the error code. */
104 // Translate high level error code.
114 // level code.
125 // If high level code is present, make a concatenation between both
141 // Translate low level error code.
/mbedtls-development/
A DBRANCHES.md27 code that's working and secure with Mbed TLS x.y.z and does not rely on
30 number, and your code will still build, be secure, and work.
39 * Returning an error code that was not previously documented for a function
41 * Changing which error code is returned in a case where multiple error
47 There are rare exceptions where we break API compatibility: code that was
57 re-compiling) and to avoid any increase in code size or RAM usage, or in the
58 minimum version of tools needed to build the code. The only exception, as
62 increase code size for a security fix.)
A DCONTRIBUTING.md11 - The code should be written in a clean and readable style.
12 - The code should be written in a portable generic way, that will benefit the whole community, and …
13 - The code should be secure, and will be reviewed from a security point of view as well.
28 …code to work with a newer version of the library. Unless the user has made an active decision to u…
42 …ional features or API extensions which may introduce issues or change the code size or RAM usage, …
68 …lable to show test coverage of the library. New code contributions should provide a similar level …
83 1. Complex parts in the code should include comments.
A DREADME.md4 …09 certificate manipulation and the SSL/TLS and DTLS protocols. Its small code footprint makes it …
49 * Python 3.6 to generate the test code, and to generate sample programs in the development branch.
81 In order to build from the source code using GNU Make, just enter at the command line:
133 - `Release`. This generates the default code without any unnecessary information in the binary fi…
134 - `Debug`. This generates debug information and disables optimization of the code.
135 - `Coverage`. This generates code coverage information in addition to debug information.
136 …code with AddressSanitizer to check for memory errors. (This includes LeakSanitizer, with recent v…
138 - `MemSan`. This instruments the code with MemorySanitizer to check for uninitialised memory read…
228 …mple programs is to demonstrate specific features of the library, and the code may need to be adap…
278 …ome parts of the code have not been reviewed as thoroughly, and some parts of the PSA implementati…
[all …]
/mbedtls-development/3rdparty/everest/
A DREADME.md3 …. The C code is automatically derived from the (verified) [original implementation](https://github…
5 … integer type and KreMLin therefore has to use additional (also verified) code to simulate them, r…
/mbedtls-development/ChangeLog.d/
A Dmuladdc-memory.txt2 * Fix missing constraints on x86_64 and aarch64 assembly code
A Dbase64-ranges.txt2 * Improve the performance of base64 constant-flow code. The result is still
A Dremove-ssl-export-keys.txt3 code size by about 80B on an M0 build. This option only gated an ability
/mbedtls-development/tests/data_files/base64/
A Ddef_b64_too_big_2.txt1 // Context with added '1234' in the middle of code to simulate too much data
A Ddef_b64_too_big_1.txt1 // Context with added '1234' at the begining to simulate too much data in the base64 code
A Ddef_b64_too_big_3.txt1 // Context with added '1234' before '==' add the end to simulate too much data in the base64 code
A Ddef_bad_b64.txt1 // Context with added extra 'A' before '==' add the end to simulate bad length of base64 code
/mbedtls-development/docs/
A D3.0-migration-guide.md6 need to change their own code in order to make it work with Mbed TLS 3.0.
129 and still relied on `compat-1.3.h` in their code.
131 Please use the new names directly in your code; `scripts/rename.pl` (from any
174 to call that from application code. However if you do (or if you want to
238 This was a trade-off between code size and countermeasures; it is no longer
239 relevant as the countermeasure is now always on at no cost in code size.
384 `mbedtls_cipher_finish()` in-between. If you code was missing that call,
608 surface, even if the code is supposedly not used.
714 code maintenance.
745 returning an error code. It is the responsibility of the application
[all …]

Completed in 25 milliseconds

123