On Sun 2019-06-09 19:17:10 +0200, Wiktor Kwapisiewicz via Gnupg-users wrote: > Hi Markus, > > On 09.06.2019 14:16, Markus Reichelt wrote: >>> in a similar fashion to what --quick-* commands already do for other actions >>> (e.g. --quick-add-uid). >> >> --set-notation maybe? > > Yes, but as far as I understand --set-notation is only a modifier that > needs to be used with another command (e.g. --quick-sign-key). > > I tried using it with my own fingerprint twice but it didn't succeed: > > $ gpg -u F470E50DCB1AD5F1E64E08644A63613A4D6E4094 --set-notation > [email protected]=zzzz --quick-sign-key > F470E50DCB1AD5F1E64E08644A63613A4D6E4094 > "Test McTestington <[email protected]>" was already signed by key > 4A63613A4D6E4094 > Nothing to sign with key 4A63613A4D6E4094 > gpg: Key not changed so no update needed.
I don't know of a way to do this automatically if there is already a certification from the current issuer over the OpenPGP User ID in question, unless the old certification is local (non-exportable), and the new one is not. in that special case, gpg seems fine with issuing the new certification (and will respect --cert-notation or --set-notation when doing so). I've opened https://dev.gnupg.org/T4584 to track this bug. Please follow up over there. --dkg
signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
