custodia.git/examples, branch master Unnamed repository; edit this file 'description' to name the repository. Add simple Keys-in-Header based authentication 2015-10-19T16:18:03+00:00 Simo Sorce simo@redhat.com 2015-10-01T13:58:40+00:00 58d434e0fea2b2f9544e7ef1fba07bf50e07b7c0 Signed-off-by: Simo Sorce <simo@redhat.com> Reviewed-by: Christian Heimes <cheimes@redhat.com> 
Signed-off-by: Simo Sorce <simo@redhat.com>
Reviewed-by: Christian Heimes <cheimes@redhat.com>
Do not use the same key for encryption and signing 2015-06-03T15:16:04+00:00 Simo Sorce simo@redhat.com 2015-06-03T15:13:03+00:00 7e7450a7a20b29d141bc9e189c6fc563a03bb6b9 using the same key for signing and encryption is generally a frown upon approach in the scirty community as it may lead to some attacks. Change the code to use key pairs, where the first key is the signing key and the second one is the encryption key. Signed-off-by: Simo Sorce <simo@redhat.com> 
using the same key for signing and encryption is generally a frown
upon approach in the scirty community as it may lead to some attacks.

Change the code to use key pairs, where the first key is the signing
key and the second one is the encryption key.

Signed-off-by: Simo Sorce <simo@redhat.com>
Add support for signed/encrypted messages 2015-04-27T19:06:26+00:00 Simo Sorce simo@redhat.com 2015-04-20T20:08:28+00:00 a2ed51acfdff399a6ad6cd486eb22da9acf59280 The new 'kem' type allows the backend to authorize access to keys based on a signed request where the key mus be whitelisted in advance in a kemkeys database. The reply is encrypted with the client public key. Signed-off-by: Simo Sorce <simo@redhat.com> 
The new 'kem' type allows the backend to authorize access to keys based on
a signed request where the key mus be whitelisted in advance in a kemkeys
database.
The reply is encrypted with the client public key.

Signed-off-by: Simo Sorce <simo@redhat.com>