Home
last modified time | relevance | path

Searched full:branches (Results 1 – 25 of 26) sorted by relevance

12

/mbedtls-3.6.0/
DCONTRIBUTING.md13 - [Backports](#long-term-support-branches): provide a backport if needed (it's fine to wait until t…
33 …n development branch and in LTS (Long Term Support) branches, as described in [BRANCHES.md](BRANCH…
41 Long Term Support Branches
43branches, which are maintained continuously for a given period. The LTS branches are provided to a…
45 When backporting to these branches please observe the following rules:
51 It would be highly appreciated if contributions are backported to LTS branches in addition to the […
53 The list of maintained branches can be found in the [Current Branches section
54 of BRANCHES.md](BRANCHES.md#current-branches).
89 …s/GPL-2.0-or-later.html) licenses. This enables LTS (Long Term Support) branches of the software t…
DBRANCHES.md1 # Maintained branches
3 At any point in time, we have a number of maintained branches, currently consisting of:
12 - One or more long-time support (LTS) branches: these only get bug fixes and
16 We retain a number of historical branches, whose names are prefixed by `archive/`,
18 These branches will not receive any changes or updates.
24 ABI compatibility within LTS branches; see the next section for details.
27 released. We may occasionally create LTS branches from other releases at our
87 ## Long-time support branches
89 For the LTS branches, additionally we try very hard to also maintain ABI
101 ## Current Branches
[all …]
DSECURITY.md16 ## Maintained branches
18 Only the maintained branches, as listed in [`BRANCHES.md`](BRANCHES.md),
D.travis.yml10 branches:
DBUGS.md10 [maintained branch](BRANCHES.md): `master`, `development`,
/mbedtls-3.6.0/include/mbedtls/
Dconstant_time.h14 /** Constant-time buffer comparison without branches.
22 * This function can be used to write constant-time code by replacing branches
/mbedtls-3.6.0/tests/scripts/
Dtest_psa_compliance.py47 #pylint: disable=too-many-branches,too-many-statements,too-many-locals
Dall.sh1913 # This tests both (1) accesses to undefined memory, and (2) branches or
1932 # This tests both (1) accesses to undefined memory, and (2) branches or
1952 # etc.) and (2) branches or memory access depending on secret values,
1986 # etc.) and (2) branches or memory access depending on secret values,
/mbedtls-3.6.0/library/
Dconstant_time_impl.h136 …* Define mask-generation code that, as far as possible, will not use branches or conditional instr… in mbedtls_ct_bool()
141 * conditional instructions or branches by trunk clang, gcc, or MSVC v19. in mbedtls_ct_bool()
Drsa_alt_helpers.h18 * Term Support) branches of Mbed TLS, but may otherwise be subject to change,
Dconstant_time.c10 * might be translated to branches by some compilers on some platforms.
Decp_internal_alt.h135 * So branches for these cases do not leak secret information.
Dmps_reader.c26 * and stores from other operations (arithmetic or branches).
Dconstant_time_internal.h547 /** Constant-time buffer comparison without branches.
Drsa.c93 * to a shared memory cache), and branches (especially visible to in mbedtls_ct_rsaes_pkcs1_v15_unpadding()
133 * buffer. Do it without branches to avoid leaking the padding in mbedtls_ct_rsaes_pkcs1_v15_unpadding()
145 /* Set ret without branches to avoid timing attacks. Return: in mbedtls_ct_rsaes_pkcs1_v15_unpadding()
Dcmac.c78 * using bit operations to avoid branches */ in cmac_multiply_by_u()
Decp.c1589 * So branches for these cases do not leak secret information.
1817 /* Adjust if needed, avoiding branches */ in ecp_comb_recode_core()
Dssl_tls12_server.c3529 /* Avoid data-dependent branches while checking for invalid in ssl_parse_encrypted_pms()
3567 * data-dependent branches. */ in ssl_parse_encrypted_pms()
Dssl_tls13_client.c299 * of PQC KEMs, we'll want to have multiple branches, one per in ssl_tls13_write_key_share_ext()
Dbignum.c1831 * observe both memory accesses and branches. However, branch prediction in mbedtls_mpi_exp_mod()
/mbedtls-3.6.0/3rdparty/p256-m/p256-m/
DREADME.md53 branches except four; three of them are reached by open-box testing using a
90 In addition to avoiding branches and memory accesses depending on secret data,
Dp256-m.c694 * branches are OK as the exponent is not a secret. in m256_inv()
974 * branches taken and memory access patterns (if observable).
1403 * Note: we're using public data only, so branches are OK in p256_ecdsa_verify()
/mbedtls-3.6.0/docs/architecture/
Dmbed-crypto-storage-specification.md347 …bed TLS is upgraded from x to y if x >= 2.25 and y < 4. See [`BRANCHES.md`](../../BRANCHES.md) for…
/mbedtls-3.6.0/scripts/mbedtls_dev/
Dcrypto_knowledge.py211 #pylint: disable=too-many-branches,too-many-return-statements
Dmacro_collector.py287 # pylint: disable=too-many-branches

12