Lines Matching refs:on
20 This document currently focuses on data structure manipulation and storage, which is what the crypt…
30 …useful in at least some configurations. Features with a significant impact on the code size or att…
32 ### Reliance on internal details
36 …on functions that aren't part of the public API. Declare such functions in `library/*.h` and inclu…
38 If test code or test data depends on internal details of the library and not just on its documented…
42 > * on top of stdio. It expects to know what the stdio name of a file is
43 > * based on its keystore name.
60 …structures, but if so, make it very clear that these fields have no impact on non-test-specific fi…
67 …should be compatible with this compile-time configuration so that it works on these alternative pl…
75 * The test function (or the whole test file) must depend on `MBEDTLS_TEST_HOOKS`.
88 …tability: tests should work on every platform. Skipping tests on certain platforms may hide errors…
109 Storage can fail, either due to hardware errors or to active attacks on trusted storage. How does t…
155 | Maintainability | !! Combinatorial explosion on the testing burden |
170 | Maintainability | ! Combinatorial explosion on the testing burden |
178 …at internal interfaces need to be used correctly. We may accidentally rely on internal details in …
180 This approach is mostly portable since it only relies on C interfaces. A limitation is that the tes…
194 … through static analysis, we don't need to test them. This puts some constraints on the properties:
196 …n the specification (but we can gain this confidence by evaluating the specification on test data).
203 | Effacement | ++ Zero impact on the code |
215 | Effacement | ++ No impact on the product when built normally or on the documentation, if done rig…
227 * **Minimize the impact on code**.<br>
241 | Effacement | ++ Zero impact on the code |
242 | Portability | ~ Depends on the method |
243 | Maintainability | ~ Depending on the instrumentation, this may require additional builds and scri…
263 | Effacement | ++ Zero impact on the code |
306 #### PSA storage cleanup on success
312 #### PSA storage cleanup on failure