Home
last modified time | relevance | path

Searched full:about (Results 1 – 25 of 135) sorted by relevance

123456

/mbedtls-latest/docs/architecture/
Dmbed-crypto-storage-specification.md11 …information about all past released versions. Do not remove information from this document unless …
39 Information about each key is stored in a dedicated file whose name is constructed from the key ide…
112 Information about each key is stored in a dedicated file designated by the key identifier. In integ…
280 The transaction file contains data about an ongoing action that cannot be completed atomically. It …
296 * 0x0001: key creation. The following locations may or may not contain data about the key that is b…
300 * 0x0002: key destruction. The following locations may or may not still contain data about the key …
401 Information about each key is stored in a dedicated file designated by the key identifier. In integ…
444 The transaction file contains data about an ongoing action that cannot be completed atomically. It …
460 * 0x0001: key creation. The following locations may or may not contain data about the key that is b…
464 * 0x0002: key destruction. The following locations may or may not still contain data about the key …
Dpsa-storage-resilience.md7 At this point, we are only concerned about one specific form of resilience: to a system crash or po…
15 …ate where the function has returned. The application never needs to worry about an intermediate st…
133 When the core starts, it needs to know about transaction(s) that need to be resumed. This informati…
157 …nt. This does not require any special precautions to preserve information about the key during the…
161 …iver design is easier: the driver doesn't need to protect the information about slots in use again…
252 …er will know if a transaction was in progress and the core cannot be sure about the state of the s…
283 In order to limit the possibilities, we need to make some assumptions about the recovery step. For …
301 As discussed in the section [“Recovery strategies”](#recovery-strategies), the information about ac…
494 …nt](#chosen-storage-invariant). In addition, if there is some information about key ongoing operat…
498 …nd does not need to (for example, it would be pointless to check anything about transparent keys).…
/mbedtls-latest/3rdparty/p256-m/p256-m/
DREADME.md15 Most cryptographic implementations care more about speed than footprint, and
32 - [Notes about other curves](#notes-about-other-curves)
33 - [Notes about other platforms](#notes-about-other-platforms)
133 Clang was also tried but tends to generate larger code (by about 10%). For
298 "Notes about other curves" below).
448 ## Notes about other curves
523 ## Notes about other platforms
526 in mind and makes a few assumptions about the platform:
/mbedtls-latest/.github/ISSUE_TEMPLATE/
Dconfig.yml5 about: Report a security vulnerability.
8 about: Mbed TLS community support and general discussion.
Dfeature_request.md3 about: To request an enhancement, please fill this form.
Dbug_report.md3 about: To report a bug, please fill this form.
/mbedtls-latest/docs/architecture/psa-migration/
Dmd-cipher-dispatch.md221 * How to obtain metadata about algorithms (e.g. hash/MAC/tag size, key size).
254 …HA256_C` is enabled, then I want RSA-PSS to support SHA-256. I don't care about negative support. …
255 …sa_crypto_not_supported` when PSA implements RSA-PSS in software, we care about negative support: …
306 * Obtain some metadata about it (size, block size).
314 …ome legacy baggage dating from when it was more open, which we don't care about anymore. This may …
358 …about it per se, they only care about getting random numbers - in fact PSA users don't even need t…
472 The `engine` field is almost redundant with knowledge about `type`. However, when an algorithm is a…
603 The `engine` field is almost redundant with knowledge about `type`. However, when an algorithm is a…
Dtesting.md23 a decision is made at run-time about whether to use the PSA or legacy code
98 However, if additional logic is involved, or there are run-time decisions about
Dpsa-legacy-bridges.md94 …r mechanisms (HMAC, signatures, key derivation, etc.). Therefore metadata about hashes is relevant…
241 * No further work is needed about RSA specifically. The amount of metadata other than hashes is suf…
242 * No further work is needed about ECC specifically. We have just added adequate functions.
243 * No further work is needed about DHM specifically. There is no good way to translate the relevant …
324 [OPEN] What about `mbedtls_pk_sign_ext` and `mbedtls_pk_verify_ext`?
Dstrategy.md18 implemented, see `docs/use-psa-crypto.md`, where new APIs are about (G2), and
66 At the time of writing (early 2022) it is unclear what could be done about the
168 on top of that layer, avoids concerns about dependency loops.
345 Since supporting driver-only builds is not about adding features, but about
/mbedtls-latest/
D.pylintrc50 # * logging-format-interpolation: Pylint warns about things like
56 # and complain about something like ``log.info('{}', foo)`` with
DSUPPORT.md3 Here are some useful sources of information about using Mbed TLS:
/mbedtls-latest/tests/scripts/
Dpsa_collect_statuses.py27 """Information about observed return statues of API functions."""
74 test suites and display information about observed return statuses.
Danalyze_outcomes.py331 # Following tests depend on AES_C/DES_C but are not about
390 # really about the wrapper around the PSA RNG, not ECDSA.
619 # We temporarily don't care about PK stuff.
633 # Following tests depend on RSA_C but are not about
702 # Following tests depend on AES_C but are not about them
Dcomponents-compiler.sh127 # Don't try to disable ASLR. We don't care about ASLR here. We do care
128 # about a spurious message if Gdb tries and fails, so suppress that.
Dall-in-docker.sh17 # See also all.sh for notes about invocation of that script.
/mbedtls-latest/tests/src/
Dhelpers.c387 * overwrite any previous information about the failure. */ in mbedtls_test_fail_internal()
455 * overwrite any previous information about the failure. */ in mbedtls_test_equal()
493 * overwrite any previous information about the failure. */ in mbedtls_test_le_u()
531 * overwrite any previous information about the failure. */ in mbedtls_test_le_s()
/mbedtls-latest/library/
Dconstant_time_impl.h31 * Disable -Wredundant-decls so that gcc does not warn about this. This is re-enabled
97 * there is no way for the compiler to ever know anything about
121 * although we don't actually care about setting the flags.
201 /* MSVC has a warning about unary minus on unsigned, but this is in mbedtls_ct_bool()
Dpsa_crypto_se.h126 * \param[in] attributes Metadata about the key that is about to be created.
Dcommon.h240 * inlined (e.g., observed about 3x perf difference in gcm_mult_largetable with gcc 7 - 12) */
250 * In some situations, this can perform better than mbedtls_xor() (e.g., it's about 5%
358 * defines static_assert even with -std=c99, but then complains about it.
/mbedtls-latest/docs/proposed/
Dpsa-conditional-inclusion-c.md209 ### Open questions about the interface
227 ### Open questions about the design
235 If a mechanism should only be supported in an opaque driver, what does the core need to know about …
239 ### Open questions about the implementation
/mbedtls-latest/include/mbedtls/
Dpkcs5.h62 * password are about 1/255).
102 * password are about 1/255).
Dpkcs12.h63 * password are about 1/255).
111 * password are about 1/255).
/mbedtls-latest/scripts/
Dapidoc_full.sh4 # available flag is documented, and avoids warnings about documentation
/mbedtls-latest/tests/git-scripts/
Dpre-push.sh20 # Information about the commits which are being pushed is supplied as lines to

123456