Home
last modified time | relevance | path

Searched refs:point (Results 1 – 25 of 38) sorted by relevance

12

/mbedtls-latest/tests/suites/
Dtest_suite_ecjpake.data25 ECJPAKE round one: KKP1: length of first point too small
28 ECJPAKE round one: KKP1: length of first point too big
31 ECJPAKE round one: KKP1: no point data
34 ECJPAKE round one: KKP1: first point is zero
37 ECJPAKE round one: KKP1: unknown first point format
40 ECJPAKE round one: KKP1: nothing after first point
43 ECJPAKE round one: KKP1: length of second point too small
46 ECJPAKE round one: KKP1: length of second point too big
49 ECJPAKE round one: KKP1: no second point data
52 ECJPAKE round one: KKP1: unknown second point format
[all …]
Dtest_suite_ecp.data61 ECP check pubkey Curve25519 low-order point #1
66 ECP check pubkey Curve25519 low-order point #2
71 ECP check pubkey Curve25519 low-order point #3 (let's call this u)
76 ECP check pubkey Curve25519 low-order point #4 (let's call this v)
81 ECP check pubkey Curve25519 low-order point #5 p-1
86 ECP check pubkey Curve25519 low-order point #6 p
91 ECP check pubkey Curve25519 low-order point #7 p+1
96 ECP check pubkey Curve25519 low-order point #8 p+u
101 ECP check pubkey Curve25519 low-order point #9 p+v
106 ECP check pubkey Curve25519 low-order point #10 2p-1
[all …]
Dtest_suite_ecp.function161 * important to test both base point and random point, though, as memory
170 * - Random point mult: ~3250M
171 * - Cold base point mult: ~3300M
172 * - Hot base point mult: ~1100M
174 * - Random point mult: ~3850M
203 /* Base point case */
218 /* Non-base point case */
1417 // Test initialized point
1424 // Test zeroed point
1431 // Set point to non-zero value
[all …]
Dtest_suite_ecdh.function4 static int load_public_key(int grp_id, data_t *point,
11 point->x,
12 point->len) == 0);
Dtest_suite_constant_time_hmac.function81 * Test all possible lengths up to a point. The difference between
Dtest_suite_pkparse.function213 /* No need to check whether the parsed public point is on the curve or
/mbedtls-latest/docs/proposed/
Dpsa-driver-interface.md57 * An object file compiled for the target platform defining the entry point functions specified by t…
79 …onstants referenced by the driver description. They may declare the entry point functions, but thi…
94 … element is the name of a [driver entry point](#driver-entry-points) or driver entry point family.…
98 …point names described by the `"entry_points"` property, to the name of the C function in the drive…
105 A driver is considered available for a cryptographic mechanism that invokes a given entry point if …
107 …y_points"` list either includes the entry point or includes an entry point family that includes th…
121 …point, algorithm, key type and key size, and all the capabilities map the entry point to the same …
123 If multiple transparent drivers have applicable capabilities for a given combination of entry point…
185 …point generally looks like the signature of the PSA Cryptography API that it implements, with some…
201 …milies that must be implemented as a whole. If a driver supports an entry point family, it must pr…
[all …]
Dpsa-driver-wrappers-codegen-migration-guide.md30 (1) psa_crypto_driver_wrappers.h will from this point on be auto generated.
/mbedtls-latest/docs/architecture/
Dpsa-storage-resilience.md7 At this point, we are only concerned about one specific form of resilience: to a system crash or po…
15 …lls an API function, as far as the application is concerned, at any given point in time, the syste…
73 1. The core calls the driver's `"allocate_key"` entry point.
76 4. The core calls the driver's key creation entry point, passing it the driver's chosen identifier …
89 2. The core calls the driver's `"destroy_key"` entry point.
137 …nt). It may call the secure element driver's `"get_key_attributes"` entry point to find out whethe…
156 …point. Recovery means resuming the operation where it left off. For key creation, this means that …
158 …requires the secure element driver to have a `"get_key_attributes"` entry point. Compared to alway…
161 …point is potentially problematic because some secure elements don't have room to store key attribu…
167 …at will go in the key file before calling the driver's key creation entry point. Therefore the nor…
[all …]
Dpsa-crypto-implementation-structure.md11 …of a core and PSA drivers as defined in the PSA driver interface. The key point is that software c…
73 …point as defined in the PSA driver interface specification are named as mbedtls_psa_<driver name>_…
141 1. API function defined in `library/psa_crypto.c`. The entry point performs generic checks that don…
Dmbed-crypto-storage-specification.md112 … integration specific) and of the key identifier (`psa_key_id_t`) from the key owner point of view.
117 …r_uid << 32 | key_id` where `key_id` is the key identifier from the owner point of view and `owner…
401 … integration specific) and of the key identifier (`psa_key_id_t`) from the key owner point of view.
406 …r_uid << 32 | key_id` where `key_id` is the key identifier from the owner point of view and `owner…
/mbedtls-latest/docs/
Dpsa-driver-example-and-guide.md16 …ions*. Single-part operations implemented by a driver will have one entry point, while multi-part …
22 …a compatible driver is present, the driver wrapper calls the driver entry point function provided …
25 … to manually edit the driver dispatch layer and call their driver's entry point functions from the…
76 …e the function in the driver dispatch layer that corresponds to the entry point of that operation.…
77 …owed by the entry point name. So, for example, the function `psa_driver_wrapper_sign_hash()` corre…
79 **5. If a driver entry point function has been provided then ensure it has the same signature as th…
80 …nd end with the entry point name. It should have the same signature as the driver wrapper function…
102 | | | | ├── foo_driver_transparent_xxx() //call to driver entry point
107 | | | | ├── bar_driver_transparent_xxx() //call to driver entry point
116 | | | | ├── baz_driver_opaque_xxx() //call to driver entry point
[all …]
/mbedtls-latest/docs/architecture/psa-thread-safety/
Dpsa-thread-safety.md171 …`q1` immediately before `f`'s linearization point, it may be `q2` immediately after `f`'s lineariz…
207 …the slot id is set. This second step is not done under the mutex, at this point the calling thread…
209 * `psa_fail_key_creation` - If there is a failure at any point in the key creation stage, this clea…
237 …point" for each call, this is a single execution step where the function takes effect (this is usu…
243 …point for a successful call is the mutex unlock within `psa_finish_key_creation`; it is at this po…
244 …point for a successful destruction is the mutex unlock, the slot is now in the state `PSA_SLOT_PEN…
245 * `psa_purge_key`, `psa_close_key` - The linearization point is the mutex unlock after wiping the s…
246 …erations - The linearization point is the final unlock of the mutex within `psa_get_and_lock_key_s…
247 * Multi-part operations - The linearization point of the key input function is the final unlock of …
320 * At this point, the destroying thread directly calls `psa_wipe_key_slot`.
[all …]
/mbedtls-latest/scripts/data_files/driver_templates/
DOS-template-opaque.jinja4 * entry_point: the name of the entry point that this function dispatches to.
5 * entry_point_param(driver): the parameters to pass to the entry point.
DOS-template-transparent.jinja4 * entry_point: the name of the entry point that this function dispatches to.
5 * entry_point_param(driver): the parameters to pass to the entry point.
/mbedtls-latest/3rdparty/p256-m/p256-m/
DREADME.md76 - "leak secret data when the input isn't a curve point" - this is avoided by
77 validating that points lie on the curve every time a point is deserialized.
303 - TinyCrypt uses Co-Z Jacobian formulas for point operation, which should be
373 - curve constants: b from the equation, the base point's coordinates;
374 - point validity check (on the curve and not 0);
376 - point doubling in Jacobian coordinates (complete formulas);
377 - point addition in mixed affine-Jacobian coordinates (P not in {0, Q, -Q});
378 - point addition-or-doubling in affine coordinates (leaky version, only used
389 negating both the scalar (mod n) and the input point if necessary.
479 gx, gy (coordinates of the base point) are hard-coded. For another curve,
[all …]
/mbedtls-latest/docs/architecture/testing/
Ddriver-interface-test-strategy.md83 …>, ..., M<sub>n</sub>). If the operation is interrupted by a reset at any point, it must be either…
85 …point (before M<sub>1</sub>, between M<sub>1</sub> and M<sub>2</sub>, ..., after M<sub>n</sub>), c…
92 This requires instrumenting the storage implementation, either to force it to fail at each point or…
129 …uest at runtime and let another driver handle the request. For each entry point, there must be at …
/mbedtls-latest/programs/test/cmake_package/
DCMakeLists.txt32 # At this point, the Mbed TLS targets should have been imported, and we can now
/mbedtls-latest/programs/test/cmake_package_install/
DCMakeLists.txt35 # At this point, the Mbed TLS targets should have been imported, and we can now
/mbedtls-latest/3rdparty/everest/library/
DHacl_Curve25519.c558 static void Hacl_EC_Format_scalar_of_point(uint8_t *scalar, uint64_t *point) in Hacl_EC_Format_scalar_of_point() argument
560 uint64_t *x = point; in Hacl_EC_Format_scalar_of_point()
561 uint64_t *z = point + (uint32_t)5U; in Hacl_EC_Format_scalar_of_point()
/mbedtls-latest/3rdparty/everest/library/legacy/
DHacl_Curve25519.c603 static void Hacl_EC_Format_scalar_of_point(uint8_t *scalar, uint64_t *point) in Hacl_EC_Format_scalar_of_point() argument
605 uint64_t *x = point; in Hacl_EC_Format_scalar_of_point()
606 uint64_t *z = point + (uint32_t)5U; in Hacl_EC_Format_scalar_of_point()
/mbedtls-latest/scripts/data_files/
Dquery_config.fmt99 * are defined empty. This means that from the preprocessor's point of view
/mbedtls-latest/
DBRANCHES.md3 At any point in time, we have a number of maintained branches, currently consisting of:
DSECURITY.md64 towards a model of fully timing-invariant code, but has not reached this point
/mbedtls-latest/docs/architecture/psa-migration/
Dmd-cipher-dispatch.md284 … call any legacy hash interface, e.g. `md.h` or `shaX.h`. There is little point in doing this, how…
497 As a starting point, return 1 if PSA crypto's driver subsystem has been initialized.
567 …l function `psa_can_do`) alongside `psa_crypto_init()`. Note that at this point, it will become a …
610 … It is only defined on algorithms that are enabled via PSA. As a starting point, return 1 if PSA c…

12