Tag Info

New answers tagged

0

Ok I had a very simple solution to that. When sending mails to myself they were automatically encrypted. When I wanted to open them I had the same error. Sidenote: They were automatically encrypted as my mailadress was known to my mail client and assigned a key. Solution: Uncheck something like "never ask for passphrase" in the enigmail settings. And then ...


0

I had the same problem: Enigmail said it couldn't find the secret key, but gpg -d just worked fine. I then discovered that I used had a custom pinentry-program defined in .gnupg/gpg-agent.conf (in my case pinentry-qt4), which I didn't have on a new installation. Removing that line or installing pinentry-qt4 solved the problem for me. In that case, the ...


1

I have not run a test on 15.04 yet. But, it sounds like something went wrong with the adding of the ppa. Could you try and remove everything (q)tox related. Add the ppa again install qtox, and run update. If that fixes things, great. I will also test the tox repo on Ubuntu 15.04 later on. here is how to remove anything tox related: Terminal First remove ...


1

To sign the code of conduct, you need to have the secret key of the key you're signing it with. Launchpad (and other key servers) only store the public key. Therefore, if you don't have the secret key of the key that's registered with your account on Launchpad, you'll need to generate a new key.


1

Your GPG secret keyring is already encrypted, though it's only as strong as your passphrase (which is true of any encryption). I'd make a tar file of all the files you want to backup (a few folders/files listed to tar, or with -T, --files-from get names to extract or create from FILE) and pipe tar's output to GPG. Basically: tar -c folder | gpg --output ...



Top 50 recent answers are included