mirror of
https://codeberg.org/openpgp/notes.git
synced 2025-09-10 11:49:40 +02:00
edit subkey binding signature, correct comma placement
This commit is contained in:
parent
c2405f53ef
commit
63fbd49dcf
1 changed files with 21 additions and 18 deletions
|
@ -266,7 +266,6 @@ In OpenPGP Signatures, there are two sets of subpacket data: hashed and unhashed
|
||||||
|
|
||||||
A subpacket data set in an OpenPGP Signature contains a list of zero or more Signature subpackets.
|
A subpacket data set in an OpenPGP Signature contains a list of zero or more Signature subpackets.
|
||||||
|
|
||||||
|
|
||||||
The following subpacket data consists of sets of "subpacket length, subpacket type ID, data." Each subpacket is displayed as one line, starting with the [subpacket type description](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-signature-subpacket-specifi) (based on the subpacket type ID). Note that bit 7 of the subpacket type ID signals if that subpacket is ["critical."](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#section-5.2.3.7-10)
|
The following subpacket data consists of sets of "subpacket length, subpacket type ID, data." Each subpacket is displayed as one line, starting with the [subpacket type description](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-signature-subpacket-specifi) (based on the subpacket type ID). Note that bit 7 of the subpacket type ID signals if that subpacket is ["critical."](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#section-5.2.3.7-10)
|
||||||
|
|
||||||
```{note}
|
```{note}
|
||||||
|
@ -339,11 +338,13 @@ This next section shows additional components of the Direct Key Signature packet
|
||||||
|
|
||||||
- `ed25519_sig`: [algorithm-specific](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-algorithm-specific-fields-for-ed2) representation of the signature (here: 64 bytes of Ed25519 signature)
|
- `ed25519_sig`: [algorithm-specific](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-algorithm-specific-fields-for-ed2) representation of the signature (here: 64 bytes of Ed25519 signature)
|
||||||
|
|
||||||
The signature's hash is calculated over the following data (see [Computing Signatures](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-11.html#name-computing-signatures) in the RFC):
|
The signature's hash is calculated from the following data:
|
||||||
|
|
||||||
- signature's salt
|
- the signature's salt
|
||||||
- serialized primary key's public data
|
- the serialized primary key's public data
|
||||||
- serialized direct key signature packet (excluding the unhashed area)
|
- the serialized direct key signature packet (excluding the unhashed area)
|
||||||
|
|
||||||
|
Refer to [Computing Signatures](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-11.html#name-computing-signatures) in the RFC for more details.
|
||||||
|
|
||||||
(zoom_enc_subkey)=
|
(zoom_enc_subkey)=
|
||||||
## Encryption subkey
|
## Encryption subkey
|
||||||
|
@ -489,22 +490,24 @@ The `pk_algo` value of this signature derives from the algorithm of the primary
|
||||||
|
|
||||||
As shown in the text at the top of this packet dump, the hashed subpacket data contains four pieces of information:
|
As shown in the text at the top of this packet dump, the hashed subpacket data contains four pieces of information:
|
||||||
|
|
||||||
- Signature creation time: `2023-09-29 15:17:58 UTC` (**critical**)
|
- signature creation time: `2023-09-29 15:17:58 UTC` (**critical**)
|
||||||
- Key expiration time: `P1095DT62781S` (**critical**)
|
- key expiration time: `P1095DT62781S` (**critical**)
|
||||||
- Key flags: `EtEr` (**critical**) (encryption for communication, encryption for storage)
|
- key flags: `EtEr` (**critical**) (encryption for communication, encryption for storage)
|
||||||
- Issuer Fingerprint: `AAA18CBB254685C58358320563FD37B67F3300F9FB0EC457378CD29F102698B3`
|
- issuer fingerprint: `AAA18CBB254685C58358320563FD37B67F3300F9FB0EC457378CD29F102698B3`
|
||||||
|
|
||||||
The remainder of the packet has the same content as the *Direct Key Signature* above:
|
The rest of the packet mirrors the *Direct Key Signature* discussed above:
|
||||||
- A 16 bit digest prefix
|
- a 16-bit digest prefix
|
||||||
- A salt value
|
- a salt value
|
||||||
- The cryptographic signature itself
|
- the cryptographic signature itself
|
||||||
|
|
||||||
The signature is calculated over a hash. The hash, in this case, is calculated over the following data (for details, see [Computing Signatures](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-11.html#name-computing-signatures) in the RFC):
|
The signature is calculated over a hash. In this case, the hash is derived from the following data:
|
||||||
|
|
||||||
- The signature's salt
|
- the signature's salt
|
||||||
- A serialized form of the primary key's public data
|
- the serialized primary key's public data
|
||||||
- A serialized form of the subkey's public data
|
- the serialized subkey's public data
|
||||||
- A serialized form of this subkey binding signature packet (up to, but excluding the unhashed area)
|
- the serialized subkey binding signature packet (excluding the unhashed area)
|
||||||
|
|
||||||
|
Refer to [Computing Signatures](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-11.html#name-computing-signatures) in the RFC for details.
|
||||||
|
|
||||||
## Signing subkey
|
## Signing subkey
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue