mirror of
https://codeberg.org/openpgp/notes.git
synced 2025-09-10 19:59:40 +02:00
edit Private key operations
This commit is contained in:
parent
f508aaa362
commit
4ddf0388ed
1 changed files with 2 additions and 2 deletions
|
@ -122,14 +122,14 @@ Notably, the practice of explicitly storing fingerprints on OpenPGP cards contra
|
|||
|
||||
## Private key operations
|
||||
|
||||
While OpenPGP as a whole employs a broad range of cryptographic mechanisms, the set of operations that are performed in the core of a private key store are simple and very limited.
|
||||
Although OpenPGP encompasses a broad range of cryptographic mechanisms, the set of operations performed within the core of a private key store are simple and very limited.
|
||||
|
||||
Specifically, an OpenPGP private key store implements two primitives:
|
||||
|
||||
1. Given private key material whose algorithm supports decryption, it can decrypt a *session key*.
|
||||
2. Given private key material whose algorithm supports signing, it can calculate a *cryptographic signature* for a hash digest.
|
||||
|
||||
All required operations can be performed with access to the component keys, including their private key material. That is, [Secret-Key packets](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-secret-key-packet-formats). Additional packets, such as binding signatures, are not required for the operations in a private key store.
|
||||
These essential operations require access only to the component keys and their associated private key material, specifically [Secret-Key packets](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-secret-key-packet-formats). Additional packets, such as binding signatures, are not required.
|
||||
|
||||
(key-store-design)=
|
||||
## Private key stores
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue