On Thu, May 04, 2023 at 09:52:54AM +0100, Andrew Gallagher wrote: > > $ gpg --group fn...@test.eu=BD9D4DEE7B2FF1CBEF2EE0C4E0ACD3E0CBE7874A > > --list-keys fn...@test.eu > > gpg: error reading key: No public key ... > —list-keys doesn’t expand groups. Try this instead: > > > andrewg@serenity % gpg --group > fn...@test.eu=BD9D4DEE7B2FF1CBEF2EE0C4E0ACD3E0CBE7874A -r fn...@test.eu -e < > /etc/shells > shells.gpg > gpg: 0x40F9B9601900E974: There is no assurance this key belongs to the named > user
I tried something like this with my MUA, I believe that doesn't work: it first looks for appropriate keys, probably using --list-keys; in fact, it insists on choosing a single key when multiple ones are available. ... > It is NOT certain that the key belongs to the person named > in the user ID. If you *really* know what you are doing, > you may answer the next question with yes. > > Use this key anyway? (y/N) y This is another issue ADK might handle differently---if gpg skipped validation of the donor keys (where ADK subkeys come from), I wouldn't have to certify any UIDs in it.
signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
