On 03/11/2019 07.52, Tony Lane via Gnupg-users wrote: > On 11/3/19 1:24 AM, Fourhundred Thecat wrote: > >> But it makes no sense. This particular private key has no passphrase. So >> shouldn't signing work in batch mode as well ? > Are you sure? Try to --edit-key and select that key (not the cert key). > Then passwd, for the empty passphrase. Don't forget to save.
I am sure the private key has no passphrase. Everything worked fine with same private key on gpg 1.4.12 But now, I cannot even list keys from secring.gpg $ gpg --list-secret-keys gpg: can't connect to the agent: No such file or directory gpg: failed to start agent '/usr/bin/gpg-agent': No such file or directory Same error when I try "--edit-key" failed to start agent '/usr/bin/gpg-agent': No such file or directory The only thing that works is "gpg --list-packets secring.gpg" $ gpg --list-packets secring.gpg | grep protect I believe this shows that secret key is not password protected If it was, it would have: protect count: protect IV: >> Also, I still get an error when trustdb.gpg is not writable. >> --lock-never > Be careful with that option. The docs say this: >> This option should be used only in very special environments >> Improper usage of this option may lead to data and key corruption. > Is there a chance that's what's happening here? well, if trustdb.gpg is not writable, how could it lead to corruption. That's the whole point. I want read-only access to trustdb.gpg, because I don't want to make any changes. _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
