Home
last modified time | relevance | path

Searched refs:section (Results 1 – 25 of 29) sorted by relevance

12

/mbedtls-latest/scripts/
Dconfig.py34 def __init__(self, active, name, value='', section=None): argument
38 self.section = section
142 setting.section)
153 def is_full_section(section): argument
155 return section.endswith('support') or section.endswith('modules')
157 def realfull_adapter(_name, active, section): argument
167 if section == 'Module configuration options':
246 def full_adapter(name, active, section): argument
248 if not is_full_section(section):
284 def baremetal_adapter(name, active, section): argument
[all …]
/mbedtls-latest/
DSECURITY.md28 In this section, we consider an attacker who can observe and modify data sent
42 and workarounds see the [Block Ciphers](#block-ciphers) section.
46 In this section, we consider an attacker who can run software on the same
73 details and workarounds see the [Block Ciphers](#block-ciphers) section.
97 In this section, we consider an attacker who has access to physical information
DLICENSE84 (except as stated in this section) patent license to make, have made,
338 Thus, it is not the intent of this section to claim rights or contest
424 If any portion of this section is held invalid or unenforceable under
425 any particular circumstance, the balance of the section is intended to
426 apply and the section as a whole is intended to apply in other
429 It is not the purpose of this section to induce you to infringe any
431 such claims; this section has the sole purpose of protecting the
440 This section is intended to make thoroughly clear what is believed to
DSUPPORT.md6 - API documentation, see the [Documentation section of the
DBRANCHES.md25 ABI compatibility within LTS branches; see the next section for details.
99 For contributors, see the [Backwards Compatibility section of
DREADME.md51 …hon is also needed to integrate PSA drivers and to build the development branch (see next section).
63 …bed TLS, but the generated files are included in official releases. This section explains how to g…
314 …le for the full text of these licenses, and [the 'License and Copyright' section in the contributi…
DCONTRIBUTING.md53 The list of maintained branches can be found in the [Current Branches section
DChangeLog909 forbidden by the standard (RFC5280 - section 4.1.2.2) and now it's being
2639 (RFC 6347 section 4.2.8): an attacker able to send forged UDP packets to
2959 rfc 5280 section 4.2.1.4.
2971 as defined in RFC 4108 section 5.
2973 RFC 5280 section 4.2.1.4. Currently, only the "Any Policy" policy is
3052 See the Features section for more information.
3375 handshake when flights do not get through (RFC 6347, section 4.1.1.1,
3596 algorithms section is too short. In builds with debug output, the overread
4502 handshake with the same context. (See RFC 6347 section 4.2.8.)
5680 * Changed certificate verify behaviour to comply with RFC 6125 section 6.3
/mbedtls-latest/docs/architecture/psa-thread-safety/
Dpsa-thread-safety.md10 …- Slot states are described in the [Key slot states](#key-slot-states) section. They guarantee saf…
13 …anagement.c` are now protected by mutexes, as described in the [Global data](#global-data) section.
23 * The [Guarantees](#guarantees) section describes the properties that are followed when PSA functio…
24 * The [Usage guide](#usage-guide) section gives guidance on initializing, using and freeing PSA whe…
25 * The [Current strategy](#current-strategy) section describes how thread-safety of key management a…
26 * The [Testing and analysis](#testing-and-analysis) section discusses the state of our testing, as …
27 * The [Future work](#future-work) section outlines our long-term goals for thread-safety; it also a…
37 …described in the [PSA Concurrent calling conventions](#psa-concurrent-calling-conventions) section.
43 …_crypto_init` has been called (see the [Initialization](#initialization) section for details on ho…
133 This section describes how we have implemented thread-safety. There is discussion of: techniques, i…
[all …]
/mbedtls-latest/docs/proposed/
Dpsa-driver-developer-guide.md28 …iption file is JSON. The structure of this JSON file is specified in the section [“Driver descript…
38 …tion](psa-driver-interface.html#driver-entry-points) except as otherwise indicated in this section.
Dpsa-driver-interface.md51 …iption file is JSON. The structure of this JSON file is specified in the section [“Driver descript…
99 …ed to fully support the mechanisms described by this capability. See the section “[Fallback](#fall…
103 … mechanism, it invokes available driver entry points as described in the section [“Driver entry po…
185 …ifications. This section gives an overview of modifications that apply to whole classes of entry p…
758 …#key-management-with-opaque-drivers). This section describes common elements. Refer to the applica…
781 … from the driver description and the key attributes, as specified in the section [“Key format for …
783 …t determine or validate the key size and set `*bits` as described in the section [“Key size determ…
785 …y points must ensure that the resulting key is valid as specified in the section [“Key validation”…
810 This section describes some minimal validity requirements for standard key types.
896 As discussed in [the general section about key management entry points](#driver-entry-points-for-ke…
[all …]
Dpsa-conditional-inclusion-c.md52 …s the feature that the symbol enables. The symbols are documented in the section [“PSA Crypto conf…
/mbedtls-latest/docs/
Ddriver-only-builds.md116 - Required hash algorithm(s) as explained in [Hashes](#hashes) section.
167 still be included in the build, see limitations sub-section below.
171 - `MBEDTLS_ECP_C` is fully removed (see limitation sub-section below),
185 limitation sub-section below).
265 Support is pretty similar to the "Elliptic-curve cryptography (ECC)" section
411 [This section depends on #8598 so it might be updated while that PR progresses.]
D3.0-migration-guide.md30 the instructions in the [Documentation section of the README](https://github.com/Mbed-TLS/mbedtls/b…
35 of these variants have been renamed without the suffix. The section
158 Please also refer to the section [High-level crypto](#high-level-crypto) for
401 Please also refer to the section [Low-level crypto](#low-level-crypto) for
614 This is described in the section [Strengthen default algorithm selection for X.509 and TLS](#streng…
857 …access is no longer supported. Please see the [section on private structure fields](#most-structur…
1020 …d TLS profiles. [RFC 8422](https://datatracker.ietf.org/doc/html/rfc8422#section-5.1.1) deprecates…
Dpsa-driver-example-and-guide.md141 … is located in the Mbed TLS source tree under `3rdparty/p256-m`. In this section, we will look at …
/mbedtls-latest/docs/architecture/psa-migration/
Dstrategy.md62 legacy APIs. However, see next section for strategies that can lower that
63 cost. The rest of this section explains the reasons for the
232 This section presents a plan towards G5: save code size by compiling out our
292 (The strategy was outlined in the previous section.)
373 This section briefly introduces questions and possible plans towards G4,
Dpsa-limitations.md34 (Regarding FFDH, see the next section as well.) See issue [3261][ffdh] on
42 (See also the first paragraph in the previous section.)
Dmd-cipher-dispatch.md273 In this section, we specify a hash metadata and calculation for the [mixed domain](#classification-…
324 This section documents things that we chose to temporarily exclude from the scope in the 3.x branch…
382 …etter code size savings and cleaner code with a new internal module (see section "Internal "block …
529 This section is not necessary to implement MD light, but will cut down its code size.
575 is needed for PSA dispatch (see next section). Note: CCM and GCM currently
/mbedtls-latest/docs/architecture/
Dalternative-implementations.md10 …ome aspects of how Mbed TLS interacts with the underlying platform. This section discusses the mai…
45 …e and array types (although they would normally be `struct` types). This section lists some known …
Dtls13-support.md77 mandatory (see section 9.1 of the specification).
133 (2) See the TLS 1.3 specific build options section below.
138 compatibility mode as defined in section D.4 of RFC 8446.
Dpsa-storage-resilience.md42 (This section was last updated for Mbed TLS 3.4.0 implementing PSA Crypto API 1.1.)
46 In this section, we use “(stateful) secure element key” to mean a key stored in a stateful secure e…
101 Note that the analysis in this section assumes that the driver does not update its persistent state…
133 …ored in a persistent “transaction list”, with one entry per key. In this section, we explore recov…
258 In this section, we discuss how to test non-atomic processes that must implement an atomic and comm…
301 As discussed in the section [“Recovery strategies”](#recovery-strategies), the information about ac…
391 This section only concerns stateful secure elements as discussed in [“Designing key management for …
Dpsa-shared-memory.md90 In this section, we briefly discuss generic countermeasures.
146 In the next section, we will analyze how susceptible various cryptographic mechanisms are to shared…
206 …mplemented: [PureEdDSA signature](https://www.rfc-editor.org/rfc/rfc8032#section-5.1.6) processes …
212 This section explains how Mbed TLS implements the shared memory protection strategy summarized belo…
382 …ared buffer is not accessed more than once by a driver function. In this section we examine variou…
496 Expand this section to document any mechanisms that bypass the copy.
/mbedtls-latest/docs/architecture/testing/
Dpsa-storage-format-testing.md52 …ddresses the test strategy for [PSA ITS over file](#psa-its-over-file) in a separate section below.
56 This section describes the desired test cases for keys created with the current storage format vers…
Dinvasive-testing.md26 See the section [“Possible approaches”](#possible-approaches) for a rationale.
65 This section explains how to replace a library function `mbedtls_foo()` by alternative code for tes…
270 This section lists some strategies that are currently used for invasive testing, or planned to be u…
Ddriver-interface-test-strategy.md25 This section describes unit tests that must be implemented to validate the secure element driver in…

12