4 ms·
I just logged this issue in Github. https://github.com/firstlookmedia/keylist-rfc https://github.com/firstlookmedia/keylist-rfc It took me a while to figure o
by AndyMcConachie 8y ago
I just logged this issue in Github.
https://github.com/firstlookmedia/keylist-rfc https://github.com/firstlookmedia/keylist-rfc
It took me a while to figure out that the server has a list of key fingerprints, yet you call it a KeyList. Perhaps call it a KeyFingerprintList. In fact the document is confusing throughout in this respect. And maybe I'm misunderstanding, but this is a mechanism for distributing fingerprints. This is not a mechanism for distributing public keys. Right?
You define "KeyList" as a list of public keys in 1.2. But then in 2.2.5 you state that the client should download the public key from a key server after finding the fingerprint in the KeyList. Is a KeyList a list of public keys or their fingerprints?
- epoch_100 8y agoThanks for bringing this up. I wonder how the naming conventions could be improved? 1.2 does mention that this is a list of public keys identified by fingerprints: > 1.2 The term "keylist" is defined as a list of OpenPGP public keys identified by their fingerprints ... Does this imply that the public keys themselves are included?
- eximius 8y agoYou could infer it describing a structure of { fingerprint : pubkey for keys in etc }. Just the name 'key list' implies a list of keys.
- epoch_100 8y agoThis makes sense. In revision 02, we will change the phrasing in section 1.2 to be something to the effect of "a list of public key fingerprints." Thanks to you both for bringing this up.