Bitcoin Forum

Bitcoin => Armory => Topic started by: Kuriso on August 22, 2017, 05:11:07 AM



Title: Question about a checksum error message
Post by: Kuriso on August 22, 2017, 05:11:07 AM
Downloading v0.96.1 to a new computer.  Taking the time to checksum.  Following the Verify Download video tutorial on bitcoinarmory.com, I have an issue.  The issue I have starts at 3:16 in the tutorial.  When I copy the whole PGP message to verify against the 0x98832223 certificate, I use the clipboard drop down and click Decrypt/Verify.  I get an "... unknown certificate..." and "The signature is invalid: No public certificate to verify the signature" message in the yellow box that opens up.

What would cause this?  I can verify that the win64 hashes match but I cannot figure out why I am getting the error message above.


Title: Re: Question about a checksum error message
Post by: HCP on August 22, 2017, 05:46:27 AM
bitcoinarmory.com is the OLD bitcoin armory website... btcarmory.com (https://btcarmory.com/) is the new "official" Armory website.

Additionally, I'm not sure if that 0x98832223 cert belongs to goatpig or the old Armory company... I suspect it is the OLD cert as according to: https://btcarmory.com/docs/verify the sig listed there is "Armory signing key (4922589A) (http://keyserver.ubuntu.com/pks/lookup?search=goatpig)"


Title: Re: Question about a checksum error message
Post by: Kuriso on August 22, 2017, 06:04:12 PM
Using that new cert works.  I didn't realize there was a company change.  I hadn't kept up with the development.

Another question...  For 0.96.1, does it not give you the option to secure download the bitcoin client within armory?


Title: Re: Question about a checksum error message
Post by: goatpig on August 22, 2017, 08:49:23 PM
Using that new cert works.  I didn't realize there was a company change.  I hadn't kept up with the development.

Another question...  For 0.96.1, does it not give you the option to secure download the bitcoin client within armory?

There's no other company, just me and a couple other volunteers basically.

The secure download feature ran on the ATI servers (former maintainer LLC). They discontinued this and I don't have access to the signing keys so the chain of updates would have been broken with my taking over anyways. As for the code itself, it involved a lot of phoning home, so I got rid of it as a whole.