Searched refs:secret (Results 1 – 9 of 9) sorted by relevance
| /Zephyr-latest/tests/crypto/secp256r1/src/ |
| D | main.c | 38 uint8_t secret[32]; in ZTEST_USER() local
46 ret = p256_ecdh_shared_secret(secret, private_key_1, public_key_2); in ZTEST_USER()
58 uint8_t secret[32]; in ZTEST_USER() local
77 secret, sizeof(secret), &secret_len); in ZTEST_USER()
86 uint8_t secret[32]; in ZTEST_USER() local
98 ret = uECC_shared_secret(public_key_2, private_key_1, secret, &curve_secp256r1); in ZTEST_USER()
|
| /Zephyr-latest/samples/tfm_integration/tfm_secure_partition/dummy_partition/ |
| D | dummy_partition.c | 17 uint8_t secret[16]; member
48 status = psa_hash_compute(PSA_ALG_SHA_256, secrets[secret_index].secret, in tfm_dp_secret_digest()
49 sizeof(secrets[secret_index].secret), digest, in tfm_dp_secret_digest()
|
| /Zephyr-latest/doc/security/ |
| D | sensor-threat.rst | 71 client must possess some kind of secret. This is generally a private
74 this secret either as part of the TLS establishment, or to sign a
77 This secret is generally generated by the service provider, or by
79 device. Policy may dictate that this secret be replaced
80 periodically, which will require a way to update the client secret.
85 of code necessary shall have access to them. [th-secret-storage]_
127 b. **Client secret changes**. Changes and new client secrets should be
191 allowed for this to be stored in the same region as the secret
193 secret storage area, and as such, more code that must be
247 the service using a secret known only to that particular device.
[all …]
|
| D | secure-coding.rst | 61 protection mechanisms cannot be kept secret on any system in
62 widespread use. Instead of relying on secret, custom-tailored
|
| D | security-overview.rst | 282 protection mechanisms cannot be kept secret on any system in
283 widespread use. Instead of relying on secret, custom-tailored
|
| /Zephyr-latest/samples/tfm_integration/tfm_secure_partition/ |
| D | README.rst | 19 partition, and retrieve a hash of the secret.
59 No valid secret for key, received expected error code
|
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 218 Key and secret management is a critical part of any secure device. You need to
|
| /Zephyr-latest/doc/security/standards/ |
| D | etsi-303645.rst | 60 - security-related secret information whose disclosure or modification can compromise
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 467 The IRK is a shared secret, distributed to peers bonded to that
|
