mirror of
https://codeberg.org/openpgp/notes.git
synced 2024-11-22 23:52:05 +01:00
edit commit 02b0785584
on the not-exactly-unique fingerprint
This commit is contained in:
parent
4a2595c5f7
commit
8c8cf2ed50
1 changed files with 1 additions and 3 deletions
|
@ -96,9 +96,7 @@ For example, an OpenPGP version 4 certificate with the fingerprint `B3D2 7B09 FB
|
||||||
Historically, even shorter 32-bit identifiers were used, like this: `2455 4239`, or `0x24554239`. Such identifiers still appear in very old documents about PGP. However, [32-bit identifiers have been long deemed unfit for purpose](https://evil32.com/). At one point, 32-bit identifiers were called "short Key ID," while 64-bit identifiers were referred to as "long Key ID."
|
Historically, even shorter 32-bit identifiers were used, like this: `2455 4239`, or `0x24554239`. Such identifiers still appear in very old documents about PGP. However, [32-bit identifiers have been long deemed unfit for purpose](https://evil32.com/). At one point, 32-bit identifiers were called "short Key ID," while 64-bit identifiers were referred to as "long Key ID."
|
||||||
|
|
||||||
```{note}
|
```{note}
|
||||||
In practice, the fingerprint of a component key is used like a unique identifier.
|
In practice, the fingerprint of a component key, while not theoretically unique, functions effectively as a unique identifier. The use of a [cryptographic hash algorithm](crypto-hash) in generating fingerprints makes the occurrence of two different component keys with the same fingerprint extremely unlikely.
|
||||||
|
|
||||||
However, formally, a fingerprint is not unique. For every component key, other component keys with the same fingerprint exist, in theory. But because fingerprints are calculated using a [cryptographic hash algorithm](crypto-hash), it is practically impossible to find two different component keys that have the same fingerprint.
|
|
||||||
```
|
```
|
||||||
|
|
||||||
### Primary key
|
### Primary key
|
||||||
|
|
Loading…
Reference in a new issue