Indeed. We would need to add different entries to the context menu for each installation. Given that GpgEX needs to be replaced anyway and we will drop the need for a UI server socket (which is anyway only a trigger and no full communication).

gpgrt 1.57 will come with gpgrt_fconcat. This can be used to get the sysconfig in a portable way:

That RFC is Experimental anyway

Still good for experiments.

Okay, forward porting that patch is the easiest solution. Actually this is not enough: Users of Libgcrypt also need to make sure that the new sysconfig dir has the right permissions. That's a part for the installer and concrete ACLs may differ.

Good catch. My guess is that get_uid_for_sender returns the last matching UID without checking for revocations. The matching was done on the mailbox part only. For reference:

Yubikeys allow that. See my mail to the mailing list.

Do you mean one of the user-ids has been revoked or the one matching the mail sender?

That is a feature not a bug. Make also sense if your threat model is store-trafic-no-decrypt-later. If you can get the key you will also be abale to get the cleartext. Any nobody can remember a passphrase on par with the claimed Kyber security level.

Can you please schek which Sqlite version you have installed? I have not seen this on my system.

Interesting. What SQlite version are you using? To see the exact reason and you have a copy of the old pubring.db, please add

The problem is that a user may unintentionally use the suggested filename without checking that it does not harm to write to this file. It is better not to present a default name at all.