$50 in BTC for person who fixes this PGP issue

I upgraded TAILS from 2.4 to 2.5. This USB had TONS of public, private keys - so decided to always back up persistence on a separate USB, just in case. Well, it happened - main USB will no longer run TAILS. I imported a few of my personal PGP pairs and they actually came in & work. The important ones (these are .asc's) - when importing into key/pass app - says something to the tune of 'this is not verified ..etc" and when I say 'dismiss', it imports it as a public key.

I tried running as admin, running terminal, going to the TailsData_unlocked vs TailsData folders and replacing - but the same result happens. I ran the script that edits ownership at the end, too. Nothing.

I NEED these keys. I need to respond to the plethora of people encrypting to me, and I need to log into PGP sites. Anyone who can walk me through getting the private PGP keys to import as a working pair like they did prior to the upgrade would be dope. And $50 richer.

Remember - I have the backup of the .asc and .pgp files on the mountable corrupt USB, as well as the backup USB. I tried importing them direct from all three sources with no luck.

Thanks all!


Comments


[5 Points] samwhiskey:

Did you try restarting your computer?


[3 Points] gcatchris:

Encrypt your private key with a long password and decrypt it on the target computer. Here's how:

First, export the public key:

gpg --output public-key.gpg --export {KEYID}

Then export the secret key and encrypt the result before it's written to disk:

gpg --output - --export-secret-key {KEYID} |\ gpg --armor --output secret-key.asc --symmetric --cipher-algo AES256

Use either a very long or just entirely random password for the encryption.

Then transfer the keys.asc on a FAT-formatted flash and shred them afterwards, or if you know how to destroy CDs (ENTIRELY), use a CD and then destroy it.

To import the key on the other machine, run:

gpg --no-use-agent --output - keys.asc | gpg --import

This will prompt for your password, then decrypt and import the key.

Make sure you destroy the encrypted file after running this! On a small file like a private key bruteforcing the password is fairly trivial and can be done in a matter of weeks to months depending on the hardware available to the attacker. The attacker's job is further simplified by the fact that the structure of a PGP private key is publicly known, so known-cleartext attacks can be attempted. If the encrypted version of your private key is leaked, revoke the key and generate a new one IMMEDIATELY.


[2 Points] None:

[removed]


[2 Points] zx88crackingforum:

Did you try putting the keys in a bag of rice?


[2 Points] chunk49:

Try moving the .pgp files you have into the ~/.gnupg folder:

user@host:~/.gnupg$ ls
gpg.conf  pubring.gpg  random_seed  secring.gpg  trustdb.gpg


[1 Points] throwahooawayyfoe:

http://imgur.com/a/yNnZK


[1 Points] stickykitty1:

Did you ever solve this issue? I'm having this exact problem right now, so frustrating! Can't import my keys on my new Tails thumb...


[1 Points] ejexe:

Try this... well, first go into a terminal with root, make sure all of the keys were imported by typing in 'gpg --list-keys'.

Assuming the ones you want are in the list, 'cd' your way to the directory where your keys are at, and type 'gpg --edit-key [EMAIL]' with an email tied to one of the accounts you need to make work.

You'll get a command line. Type 'trust', press enter. Make sure it is your key (though idk how it would be anyone else's), type '5' (or '4', whichever is 'full'/'ultimate' trust) and press enter. Verify that you want to change the trust, and you'll get back to the cmd line. Type 'quit', press enter.

Hope it helps, I know I've had this problem before. You could also try to copy the whole /.gnupg folder from the old flash drive to the new one. That would likely be the easiest scenario, but you might have done that already..


[-3 Points] VarietyCombs:

.


[-2 Points] VarietyCombs:

Hahaha