[openpgp] Re: [Dance] Key digest companion for RFC 7929 OPENPGPKEY
Andrew Gallagher <[email protected]> Thu, 20 Nov 2025 23:29:34 +0000
| Newsgroups | gmane.ietf.openpgp |
|---|---|
| Message-ID | <[email protected]> |
Original full message seems to be here: https://mailarchive.ietf.org/arch/msg/dance/BE0eYcuqKjTnowxyJFVCR08RDw0/ — Andrew Gallagher > On 20 Nov 2025, at 23:07, Paul Wouters <[email protected]> wrote: > > On Wed, 19 Nov 2025, Petr Menšík wrote: > > [ Adding openpgp to CC: so we can start dropping dance from this later ] > >> I think it would be nice to have something like SSHFP for SSH key. Software working with PGP works by intentifying keys by their digest. PGP key can be potentially large. It is wasting of connectivity to make repeated key requests, when I am interested only in information that the key is still the latest. > > OpenPGP keys can have various things in them. For example other people's > signatures vouching for the key. Or optional attributes like photos. For > you to determine you have to same key to run the hash over to get the > same fingerprint, you have to remove all that data and strip the key to > its minimum. At which point, why not push that into the existing OPENPGP > record? > >> Example: >> >> # [email protected] >> 72dec291ea5c80f07dca832be132f5c6cb6d43713ec4843dff82d7ee._openpgpkey.fedoraproject.org. IN OPENPGPFP 2 C6E7F081CF80E13146676E88829B606631645531 >> >> This could make more efficient way to query ID of current key. If you have the key already, fetching the key each time again is wasting. > > Such a prefix seems odd. It makes querying harder if there is a key > update. Using the OPENPGPKEY method based on unique email address seems > more robust to me. > > Paul > > _______________________________________________ > openpgp mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ openpgp mailing list -- [email protected] To unsubscribe send an email to [email protected]