I have no experience with Kleopatra, so I cant help you there.
With GnuPG it should be the same as on linux. You first need to import the public key. --import keyID usually does it. If you try to verify it should tell you the ID of the key. You can either download the key via a keyserver or download it manually and import from the file.
Topic: Help a noob validating the bitcoin installer (Read 499 times)
Hello,
I spent a few hours troubleshooting this to no avail. I want to validate my download of the 0.9.1 client. I run windows 7. I have GnuGPG and Kleopatra installed, and have used it to successfully verify other installers before, like my litecoin client and Truecrypt. And I validated the previous bitcoin client, so I'm not sure what gives.
Here's what I do:
- In Cleopatra, I go to decrypt/verify, and select the SHA256SUMS.asc file. I have "input file is a detached signature" checked. Then I browse to the executable to set the path in the field beneath, for "signed data".
The program returns "no signatures found" when I run this... If I open the .asc file in notepad, there is clearly a PGP signature in there.
When I try in command line, running gpg --verify, gpg returns : "can't check signature, no public key"
So it seems I get different feedback when doing this through Kleopatra and command line. I have imported Gavin Andresen's key in kleopatra, by the way. So I'm not sure what I'm doing wrong at this point... I looked online for walkthroughs, but none yielded the right results, most of them were for Linux anyways.
Any help would be great. In fact, I'm surprised there isn't such information on the bitcoin site. This is the kind of thing that is paramount to making bitcoin friendlier to the masses.
I spent a few hours troubleshooting this to no avail. I want to validate my download of the 0.9.1 client. I run windows 7. I have GnuGPG and Kleopatra installed, and have used it to successfully verify other installers before, like my litecoin client and Truecrypt. And I validated the previous bitcoin client, so I'm not sure what gives.
Here's what I do:
- In Cleopatra, I go to decrypt/verify, and select the SHA256SUMS.asc file. I have "input file is a detached signature" checked. Then I browse to the executable to set the path in the field beneath, for "signed data".
The program returns "no signatures found" when I run this... If I open the .asc file in notepad, there is clearly a PGP signature in there.
When I try in command line, running gpg --verify, gpg returns : "can't check signature, no public key"
So it seems I get different feedback when doing this through Kleopatra and command line. I have imported Gavin Andresen's key in kleopatra, by the way. So I'm not sure what I'm doing wrong at this point... I looked online for walkthroughs, but none yielded the right results, most of them were for Linux anyways.
Any help would be great. In fact, I'm surprised there isn't such information on the bitcoin site. This is the kind of thing that is paramount to making bitcoin friendlier to the masses.
Jump to: