I could use some help from people who are more expert at GnuPG than I am, which is most people. Using GnuPG 2.0.26 and libcrypt 1.6.2, running under Gentoo with kernel 3.17.4, all at the command line. I have a gpg key (since 2004) and it's always worked well for me. Just today, though, I tried to use it to decrypt a file I'd successfully decrupted many times in the past: $ gpg -d File_to_Decrypt > decrypted_file I kept getting a "bad session key" error. After doing some googling, I eventually tried the suggestion to run: $ gpgconf --reload After doing so, however, when I try to decrypt the file as before: $ gpg -d File_to_Decrypt > decrypted_file gpg now asks for the data file, and when I offer File_to_Decrypt, I get back a list of of signatures, each correctly identified with my DSA key ID (as shown by the command gpg --listkeys), but each entry is followed by the line "BAD signature from <my_ID> [ultimate]" -- which seems like very bad news indeed. Naturally, the encrypted file is valuable (to me), and I have backup encrypted copies, but nothing in clear... Well, the gnupg key hasn't changed since February 2004, and it's worked fine all the way to at least mid-October 2014, the last time I encrypted/decrypted the file. Now I'm more or less clueless. What should I try next? -- Peter King peter.king@utoronto.ca Department of Philosophy 170 St. George Street #521 The University of Toronto (416)-978-3311 ofc Toronto, ON M5R 2M8 CANADA http://individual.utoronto.ca/pking/ ========================================================================= GPG keyID 0x7587EC42 (2B14 A355 46BC 2A16 D0BC 36F5 1FE6 D32A 7587 EC42) gpg --keyserver pgp.mit.edu --recv-keys 7587EC42