Gilles Peskine 224b0d656a Key derivation: allow both keys and direct inputs ... Allow a direct input as the SECRET input step in a key derivation, in addition to allowing DERIVE keys. This makes it easier for applications to run a key derivation where the "secret" input is obtained from somewhere else. This makes it possible for the "secret" input to be empty (keys cannot be empty), which some protocols do (for example the IV derivation in EAP-TLS). Conversely, allow a RAW_DATA key as the INFO/LABEL/SALT/SEED input to a key derivation, in addition to allowing direct inputs. This doesn't improve security, but removes a step when a personalization parameter is stored in the key store, and allows this personalization parameter to remain opaque. Add test cases that explore step/key-type-and-keyhood combinations.		2019-09-24 18:39:03 +02:00
..
mbedtls	Merge pull request #185 from gilles-peskine-arm/harvard-md	2019-09-10 18:38:39 +01:00
psa	Key derivation: allow both keys and direct inputs	2019-09-24 18:39:03 +02:00
.gitignore
CMakeLists.txt	3rdparty: Add additional build facilities for 3rd-party code	2019-08-19 13:37:46 +01:00