Lines Matching refs:size

24 …rticular combination of parameters (cryptographic algorithm, key type and size, etc.), it is used …
83 …transparent drivers, optional for opaque drivers, integer or string). The size in bytes of the [pe…
119 * or the value of the capability's `"key_sizes"` property includes the key's size.
121size, and all the capabilities map the entry point to the same function name, the driver is consid…
123 …ities for a given combination of entry point, algorithm, key type and key size, the first matching…
190 3. `size_t key_buffer_size`: the size of the key buffer in bytes.
198 2. `size_t key_buffer_size`: the size of the key buffer in bytes.
209 …t8_t *` and is immediately followed by a parameter of type `size_t` that indicates the buffer size.
210 …iately followed by a parameter of type `size_t` that indicates the buffer size. A third parameter …
211 …iately followed by a parameter of type `size_t` that indicates the buffer size. In-out buffers are…
213 Buffers of size 0 may be represented with either a null pointer or a non-null pointer.
373 …g. Call `psa_crypto_driver_key_derivation_get_input_size()` to obtain the size of the input data. …
381 size_t *size);
401 … `psa_crypto_driver_key_derivation_get_input_size`, the core sets `*size` to the size of the speci…
403 …nter to a buffer containing the key context and `*key_buffer_size` to the size of the key context …
408 …as been copied to the output parameter (`size`, `buffer`, `value` or `p_key_buffer`) and if applic…
411 … larger buffer. Call `psa_crypto_driver_key_derivation_get_input_size` to obtain the required size.
497 …when deriving a cooked (non-raw) key as described below, or if the output size exceeds some implem…
512 * `"derived_sizes"` (optional, list of integers). Each element is a size for the derived key, in bi…
528 … attributes of the specified key. Note that only the key type and the bit-size are guaranteed to b…
531 …export format](#key-format-for-transparent-drivers) for the key type. Its size is `key_buffer_size…
546 * `PSA_KEY_TYPE_ECC_KEY_PAIR(…)`, `PSA_KEY_TYPE_DH_KEY_PAIR(…)`: $m$ bytes, where the bit-size of t…
671 …n with a larger buffer. Call `psa_crypto_driver_pake_get_password_len` to obtain the required size.
700 * `output_size` size of the output buffer in bytes.
781size of the key data buffer `key_buffer` is sufficient for the internal representation of the key.…
783 …etermine or validate the key size and set `*bits` as described in the section [“Key size determina…
787 #### Key size determination on import
789 The `"import_key"` entry point must determine or validate the key size.
790 The PSA Cryptography API exposes the key size as part of the key attributes.
791size recorded in the key attributes can be either a size specified by the caller of the API (who m…
793size passed by the caller of `psa_import_key`. If this size is `0`, the `"import_key"` entry point…
796size from the data and set `*bits` to this size. If the key size cannot be determined from the dat…
803size, or if the keying material involves integers that have to be in a certain range, key creation…
812 * For symmetric key types, check that the key size is suitable for the type.
814 …ecks? Value ranges (e.g. p < n), sanity checks such as parity, minimum and maximum size, what else?
815 * For elliptic curve private keys (`PSA_KEY_TYPE_ECC_KEY_PAIR`), check the size and range. TODO: wh…
816 * For elliptic curve public keys (`PSA_KEY_TYPE_ECC_PUBLIC_KEY`), check the size and range, and tha…
834 * `output_size`: the size of the `output` buffer in bytes. This size should be large enough to allo…
865 …n `"init"` entry point in a capability with no algorithm, key type or key size. If so, the core ca…
911 3. [Determine the key size](#key-size-determination-on-import) and output it through `*bits`.
932 …n) when the driver runs out of entropy. This value is also a hint for the size to supply if the co…
962 * `entropy_size`: the size of the `entropy` buffer in bytes. It is guaranteed to be at least `1`, b…
971 …cessive calls to the `"add_entropy"` entry point. If the required entropy size is zero, the core d…
977 …th an estimated amount of entropy that is in general less than the buffer size. The core must appl…
1007 * `output_size`: the size of the `output` buffer in bytes.
1042 …evel-element) specifies how to calculate the size of the key context as a function of the key type…
1047 …): every key context for a symmetric key includes this many times the key size. If omitted, this v…
1050 …er methods (including the `"size_function"` entry point) to determine the size of the key context …
1056 …and the driver specification includes the `"size_function"` property, the size of the key context …
1060 …ty, `key_type` is the key type and `key_bits` is the key size in bits. The prototype of the size f…
1067 …include the `"size_function"` property, the size of the key context for a key of type `key_type` a…
1084 where `key_bytes = ((key_bits + 7) / 8)` is the key size in bytes.
1086 #### Key context size for a secure element with storage
1088 … driver only needs to store a label for the key, use `"base_size"` as the size of the label plus a…
1090 …_key"` property with the value `true`. Note that this only influences the size of the key context:…
1092 #### Key context size for a secure element without storage
1209 … If the key context includes the public key, it needs to have an adequate size; see [“Key format f…
1211size of the output buffer (`data_size`) is sufficient to export any key with the given attributes…
1215 …paque driver. This persistent state consists of a single byte array whose size is given by the `"p…
1217 …ialization). It is adjusted to match the size declared by the driver, in case a driver upgrade cha…
1220 * If the stored persistent state is smaller than the declared size, the core pads the persistent st…
1221 …rsistent state is larger than the declared size, the core truncates the persistent state to the de…
1255 …e` has this value, otherwise `key_buffer_size` has the value determined from the key type and size.
1332 …ble that the core would want to statically allocate an array of the given size, the core needs to …
1365 Should 0-size buffers be guaranteed to have a non-null pointers?
1369 …hould the core guarantee that the output buffer size has the size indicated by the applicable buff…
1406 …driver presumably handles it more efficiently (in terms of speed and code size) than the core coul…
1408 …t: the core can't know the size of the key representation until it knows the bit-size of the key, …