[openpgp] Re: [Dance] Key digest companion for RFC 7929 OPENPGPKEY

Hi, Petr.

On 21/11/2025 11:33, Petr Menšík wrote:
> 
> Yes, that is exactly what I wanted. That is why I propose to publish 
> fingerprint used as key handle by software I use. Key data modification 
> should not change the id presented by OPENPGPFP. Only generation of 
> different key should cause that. That should provide strong indication 
> to user he should fetch a new key again.

Great, so we're only considering the "owner has generated a new key" use 
case. :-) But see below...

> I am only user of PGP, do not 
> know correct terminology for important details. I have read couple of 
> DNS RFCs, but never read any PGP RFC. Sorry if my terms are little 
> misguiding.

Don't worry about it! Even experienced OpenPGP people get the 
terminology confused sometimes, it's a hazard of the job... ;-)

> Ah, okay, timestamp of last the change might be enough. Except it 
> depends on correct time of the machine storing that change. At least gpg 
> --list-keys does not print any timestamp of last modification.

Wouldn't this fall under the "owner has modified his existing key" use 
case which is out of scope?

I was thinking of the last modification time of the DNS record(s), not 
of the key metadata. This would not require any integration with OpenPGP 
tooling, just with DNS tooling, and could be generalised to other DNS 
use cases.

A

_______________________________________________
openpgp mailing list -- [email protected]
To unsubscribe send an email to [email protected]