| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Signed-off-by: Simo Sorce <simo@redhat.com>
Reviewed-by: Christian Heimes <cheimes@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>
|
|
|
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>
|
