Silk Road forums
Discussion => Security => Topic started by: MrFibonacci on December 31, 2012, 07:12 pm
-
I've sent a message to two different sellers multiple times now and every time they try to decrypt it they get this error.
'Decrypt failed! (No secret key)
Code = 17'
I did this this for months with no problems. I took a break for a while and encrypted my message the same way I always have and this started happening. 1- Copy and paste user's public key to note pad and save 2- Import user's key to PGP 3- Write message in a new notepad that I wish to encrypt 4- In the task bar find PGP, right click it, click 'current window', and 'encrypt' 5- Choose the corresponding user's key I wish to send the message to and ecrypt it 6- Copy and paste this encryption in the medium I send it to them though and send it
The only thing I could think of that might have changed is I messed around with my PGP after I stopped using it and I needed my passphrase, but I'd forgot it because I never had to use it. I thought maybe that had something to do with "no secret key." I created a new master key with a new passphrase and they both got the same error again! So I started completely over. I uninstalled PGP and erased all my keyrings. I even removed my key from the database online and made a new key from scratch. Same error!!!!!!
WTF!?
-
I've sent a message to two different sellers multiple times now and every time they try to decrypt it they get this error.
'Decrypt failed! (No secret key)
Code = 17'
I did this this for months with no problems. I took a break for a while and encrypted my message the same way I always have and this started happening.
1- Copy and paste user's public key to note pad and save
2- Import user's key to PGP
3- Write message in a new notepad that I wish to encrypt
4- In the task bar find PGP, right click it, click 'current window', and '
encrypt'
5- Choose the corresponding user's key I wish to send the message to and ecrypt it
6- Copy and paste this encryption in the medium I send it to them though and send it
The only thing I could think of that might have changed is I messed around with my PGP after I stopped using it and I needed my passphrase, but I'd forgot it because I never had to use it. I thought maybe that had something to do with "no secret key." I created a new master key with a new passphrase and they both got the same error again! So I started completely over. I uninstalled PGP and erased all my keyrings. I even removed my key from the database online and made a new key from scratch. Same error!!!!!!
WTF!?
<Sigh> The ONLY reason two or more vendors would get an error saying "No secret key" is if you failed to encrypt the message to their keys. No ifs, no ands, no buts.
Do yourself a favor and download GPG4USB, and then to Astor's tutorial:
GPG4USB homepage: http://gpg4usb.cpunk.de/index.html
Astor's GPG4USB Tutorial: http://32yehzkk7jflf6r2.onion/gpg4usb/
It's easy enough to confirm what you've been doing -- just send me a message with the following:
1) Both of the vendor's public keys
2) Your PGP public key.
3) An arbitrary text message encrypted to their vendor's keys the same way you've described above.
I won't be able to decrypt the message, but I will be able to determine which keys it is encrypted to.
NC
-
Could the failure message have actually said 'No public key'? That would mean you 'signed' your message and the vendor has not imported your public key.
Best to not sign messages for our purposes here on the SR. I think 100% of my customer's PGP issues have been resolved by asking them to re-encrypt without signing.
-
Could the failure message have actually said 'No public key'? That would mean you 'signed' your message and the vendor has not imported your public key.
Best to not sign messages for our purposes here on the SR. I think 100% of my customer's PGP issues have been resolved by asking them to re-encrypt without signing.
Unlikely. Code 17 is the error message for "no secret key".
NC
-
Could the failure message have actually said 'No public key'? That would mean you 'signed' your message and the vendor has not imported your public key.
Best to not sign messages for our purposes here on the SR. I think 100% of my customer's PGP issues have been resolved by asking them to re-encrypt without signing.
Unlikely. Code 17 is the error message for "no secret key".
NC
Right on - good of you to check that. I wonder what would happen if he didn't include himself as a recipient. Who's public key would it use to encrypt?
-
Could the failure message have actually said 'No public key'? That would mean you 'signed' your message and the vendor has not imported your public key.
Best to not sign messages for our purposes here on the SR. I think 100% of my customer's PGP issues have been resolved by asking them to re-encrypt without signing.
Unlikely. Code 17 is the error message for "no secret key".
NC
Right on - good of you to check that. I wonder what would happen if he didn't include himself as a recipient. Who's public key would it use to encrypt?
That's the whole problem... we don't know to whose keys the message was encrypted.
NC