Home
last modified time | relevance | path

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

/mbedtls-3.5.0/scripts/
Dconfig.py45 def __init__(self, active, name, value='', section=None): argument
49 self.section = section
153 setting.section)
164 def is_full_section(section): argument
166 return section.endswith('support') or section.endswith('modules')
168 def realfull_adapter(_name, active, section): argument
178 if section == 'Module configuration options':
246 def full_adapter(name, active, section): argument
248 if not is_full_section(section):
281 def baremetal_adapter(name, active, section): argument
[all …]
/mbedtls-3.5.0/
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
DSUPPORT.md6 - API documentation, see the [Documentation section of the
DBRANCHES.md24 ABI compatibility within LTS branches; see the next section for details.
93 For contributors, see the [Backwards Compatibility section of
DCONTRIBUTING.md53 The list of maintained branches can be found in the [Current Branches section
87 …se header where possible. For licensing details, please see the [License section of the README](RE…
DLICENSE77 (except as stated in this section) patent license to make, have made,
DREADME.md59 …bed TLS, but the generated files are included in official releases. This section explains how to g…
DChangeLog133 forbidden by the standard (RFC5280 - section 4.1.2.2) and now it's being
1863 (RFC 6347 section 4.2.8): an attacker able to send forged UDP packets to
2183 rfc 5280 section 4.2.1.4.
2195 as defined in RFC 4108 section 5.
2197 RFC 5280 section 4.2.1.4. Currently, only the "Any Policy" policy is
2276 See the Features section for more information.
2599 handshake when flights do not get through (RFC 6347, section 4.1.1.1,
2820 algorithms section is too short. In builds with debug output, the overread
3726 handshake with the same context. (See RFC 6347 section 4.2.8.)
4904 * Changed certificate verify behaviour to comply with RFC 6125 section 6.3
/mbedtls-3.5.0/docs/proposed/
Dpsa-driver-developer-guide.md27 …iption file is JSON. The structure of this JSON file is specified in the section [“Driver descript…
37 …tion](psa-driver-interface.html#driver-entry-points) except as otherwise indicated in this section.
Dpsa-driver-interface.md49 …iption file is JSON. The structure of this JSON file is specified in the section [“Driver descript…
97 …ed to fully support the mechanisms described by this capability. See the section “[Fallback](#fall…
101 … mechanism, it invokes available driver entry points as described in the section [“Driver entry po…
183 …ifications. This section gives an overview of modifications that apply to whole classes of entry p…
495 …#key-management-with-opaque-drivers). This section describes common elements. Refer to the applica…
517 … from the driver description and the key attributes, as specified in the section [“Key format for …
519 …t determine or validate the key size and set `*bits` as described in the section [“Key size determ…
521 …y points must ensure that the resulting key is valid as specified in the section [“Key validation”…
546 This section describes some minimal validity requirements for standard key types.
632 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-3.5.0/docs/architecture/
Dtls13-support.md8 the "Support description" section below. The TLS 1.3 support enablement
15 development branch into the prototype. The section "Prototype upstreaming
85 mandatory (see section 9.1 of the specification).
147 (2) See the TLS 1.3 specific build options section below.
152 compatibility mode as defined in section D.4 of RFC 8446.
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 …
/mbedtls-3.5.0/docs/architecture/psa-migration/
Dstrategy.md56 legacy APIs. However, see next section for strategies that can lower that
57 cost. The rest of this section explains the reasons for the
219 This section presents a plan towards G5: save code size by compiling out our
224 enabled (see previous section): MD and Cipher.
288 (The strategy was outlined in the previous section.)
404 This section briefly introduces questions and possible plans towards G4,
Dpsa-limitations.md30 (Regarding FFDH, see the next section as well.) See issue [3261][ffdh] on
38 (See also the first paragraph in the previous section.)
Dmd-cipher-dispatch.md217 In this section, we specify a hash metadata and calculation for the [mixed domain](#classification-…
437 This section is not necessary to implement MD light, but will cut down its code size.
/mbedtls-3.5.0/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…
/mbedtls-3.5.0/docs/
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…
/mbedtls-3.5.0/tests/suites/
Dtest_suite_psa_crypto.function125 * as defined by PKCS#1 v2.2 (RFC 8017) section A.1.2: