Re: Adding new uid to causes bad signature
Hi, I have tried to replicate your issue using a Yubikey 5 NFC, doing what you did. > In general, I don't think my procedure for adding a new uid is abnormal: > $ gpg --edit-key 408FB2EBC3DF3DBBE0143D9A29AD46D6F58287A3 > gpg> adduid > gpg> save For my key and using gpg 2.4.5 on a standard Windows 10 system "check" didn't give an error and signing a document worked without any issues. I used a simple brainpool standard testkey with only one subkey, though. > General info: > OS: Windows 11 (AtlasOS) & MacOS 14.1.1 (tried on both) > GPG: GPG 2.4.4.-unknown (bundled with git-scm windows installer), GPG > 2.4.5 (homebrew) > > My public keys: > Before trying to add a new uid: > After trying to add a new uid: Importing your second pubkey did not change anything noticeable, gpg reported no changes on the key and there is no new UID to be seen. So it seems it was not exported. To avoid any confusion does gpg -k 408FB2EBC3DF3DBBE0143D9A29AD46D6F58287A3 show the new UID for you? Is there additional info if you add "--list-options show-unusable-uids" before the "-k"? Regards Eva -- g10 Code GmbH GnuPG.com AmtsGer. Wuppertal HRB 14459 Bergstr. 3a Geschäftsführung Werner Koch D-40699 Erkrath https://gnupg.com USt-Id DE215605608 ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: No secret key
Hi, First of all: The usual procedure when asking for advice is to tell us which gpg version you are using. And on which operation system. But it seems likely that in this case the info is not necessary. > I received this message when using --clear-sign. > gpg: no default secret key: No secret key > gpg: clear-sign dialed: No secret key Please always post complete gpg comand lines and the corresponding output - you can of course obfuscate names and other personal info. I assume you have entered something like: gpg --clear-sign test.txt without specifiying the key to use on the command line and no default key defined in you gpg.conf. The gpg man page describes how to specify that key: --clearsign Make a cleartext signature. The content in a cleartext sig‐ nature is readable without any special software. OpenPGP software is only needed to verify the signature. cleartext signatures may modify end-of-line whitespace for platform in‐ dependence and are not intended to be reversible. The sign‐ ing key is chosen by default or can be set explicitly using the --local-user and --default-key options Therefore, If you did not set a default key in your gpg.conf, you have to provide the key to use on the command line as described. Regards Eva ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: gpg --card-edit cuts secret keys
Hi Carsten, On Sonntag, 10. September 2023 20:56:44 CEST Carsten Grohmann via Gnupg-users wrote: > Is this an expected behaviour? Can I control it? if you mean by truncated shadowed, then it is this bug: https://dev.gnupg.org/T6386 It will fixed for the 2.2 branch in 2.2.42 The bug does not occur in the stable 2.4. branch which is the recommended branch to use. Regards, Eva ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
