Lines Matching refs:shared

1 PSA API functions and shared memory
6 …s that are in memory that is shared with an untrusted process. On such systems, the untrusted proc…
13 …erview/conventions.html#output-buffer-sizes). Any other data is assumed to be in non-shared memory.
21 …nments where the arguments passed to a PSA Crypto API function may be in shared memory (as opposed…
31 * a crypto service, which offers PSA crypto API calls over RPC (remote procedure call) using shared…
39 If an input argument is in shared memory, there is a risk of a **read-read inconsistency**:
45 …ithout validation. A malicious client can modify the length field in the shared memory between the…
54 If an output argument is in shared memory, there is a risk of a **write-read inconsistency**:
66 If an output argument is in shared memory, there is a risk of a **write-write disclosure**:
74 …shared key. Clients are not allowed to access each other's data. The provisioning application isol…
78 If a function both has an input argument and an output argument in shared memory, and processes its…
96 … the copy away, if it does not understand that copies between shared memory and non-shared memory …
98 Example: the PSA Firmware Framework 1.0 forbids shared memory between partitions. This restriction …
102 The following rules guarantee that shared memory cannot result in a security violation other than […
126 > In an environment with multiple threads or with shared memory, the implementation carefully acces…
128 In Mbed TLS 2.x and 3.x up to and including 3.5.0, there is no defense against buffers in shared me…
134 …od is to ensure that drivers have no access to shared memory. This means that any buffer located i…
138 It is ok to skip the copy if it is known for sure that a buffer is not in shared memory. However, t…
146 In the next section, we will analyze how susceptible various cryptographic mechanisms are to shared…
210 ## Design of shared memory protection
212 This section explains how Mbed TLS implements the shared memory protection strategy summarized belo…
216 … copy of the following buffers, so that drivers do not receive arguments that are in shared memory:
289 This is fairly self-explanatory. Review all functions that use shared memory and ensure that they e…
382 …curity issue. Specifically, we must check that each memory location in a shared buffer is not acce…
494 …the copy and process buffers directly in builds that are not affected by shared memory considerati…
616 …at function as no-ops. Since buffer copying is specific to systems where shared memory is passed t…