Quote from: truy on October 02, 2013, 03:30:19 AM

Canton, can you confirm the recent changes on the website?

sha1sum:
dbcaf6ff3a8b0bf1bd213272884b8a6c945dc678 - current website
a64a1bde6be1a0120984da9acf8d031842dc4f68 - current git code and website before change

Thanks.

Sorry for the confusion here, I think you might have noticed that for a few days, bitcoinpaperwallet.com (the live website) was a little more up-to-date than the git code. This is because I was soliciting feedback before pushing some significant Oct 1 version changes to github. (For example, you can now use your own keys / vanitygen and you aren't obligated to use the built-in random key generator.)

At the time I'm writing this, both the website and the github code should be identical. I'd post the SHA1SUM here, but what I prefer is for you to check the GPG signature that is distributed with the github zip code:

Quote

After downloading the ZIP package for this generator, you should find a file named generate-wallet.html.sig which you can use to:

1) verify that generate-wallet.html hasn't been tampered with, and

2) get proof that it really was authored by Canton Becker (canton@gmail.com) whose public key and fingerprint can be confirmed at cantonbecker.com, bitcointalk.org, etc.

For example, if you have GPG installed, just open the terminal, change directory (cd) to where this generate-wallet.html lives, and type:
gpg --verify --with-fingerprint generate-wallet.html.sig generate-wallet.html

The reason I prefer the GPG signature method is that it's not vulnerable to situations like bitcointalk.org getting hacked and having its posts modified. Not that this could ever happen of course, because bitcointalk.org never gets hacked. Wink