-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 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. > 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? -----BEGIN PGP SIGNATURE----- iLcEARMKAB0WIQQWZv6JZKxO310TWtXo8fj9gx4T0wUCXb55QgAKCRDo8fj9gx4T 0wIGAgUReI7Epg4xygz0BxRkl+TSUwSW6K7q98D6AlkbjLbHUZBEG2RfmRu9IINe UF3BFVddL1XqxV593DR81PPfU/gF+QIIrlMAvOW0kl/45S1cUrsrG9UkDMIRuM7i NniVfZ9Snj5RZSVIdZNHw9wwdKKkY1MujkqfdF9UL4mtzIl1RQ8EFo0= =dO9l -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
