<p>These steps can be simplified if you use UNIX, as most of the tools are already available. However I assume you use Windows.
For PGP explanation, search for videos on youtube.</p>

<p>These steps are for the webpage bitaddress.org.  </p>

<p>For the PGP part:<br>
1. Download and install Gpg4win.<br>
2. Go to bitaddress.org and click on the link at the bottom to go to Github Repsitory.<br>
3. On their Github page, click on 'CHANGELOG.txt.asc', then click on the 'raw' tab.<br>
4. Right-click and save as.<br>
5. Run Kleopatra(Gpg4win).<br>
6. Click on Decrypt/Verify tab.<br>
7. Find the CHANGELOG file you just downloaded and 'open'.<br>
8. Now click on the 'search' tab, since you are missing the public key to verify the message.<br>
9. The public key for ninja should have been found, click to import it.<br>
10. Click OK/YES when asked to certify the fingerprints, we know it is the correct ones since the key fingerprint is posted on <a href="https://bitcointalk.org/index.php?topic=43496.0" rel="nofollow noreferrer">https://bitcointalk.org/index.php?topic=43496.0</a> .<br>
11. You will be asked to create a account, click yes.<br>
12. Type whatever you want(not important).<br>
13. Create a simple password.<br>
14. Click 'finish'.<br>
15. Select all the IDs, and then tick the box ' I have verified the fingerprint'and next.<br>
16. Click certify.<br>
17. Enter the password you just created.<br>
18. You will get certification successfull, click finish.<br>
19. Now you will be shown if the contents inside CHANGELOG is valid.<br>
20. If you get "The signature is valid and the certificate's validity is fully trusted." Then we know that the file content is authentic and hasn't been tampered with.<br>
21. So now we know that the file CHANGELOG.txt.asc inside their Github is authentic. We can process to the SHA256 part.    </p>

<p>For the SHA256 part:<br>
1. Go to bitaddress.org and right-click and save as 'Webpage HTML only'<br>
2. Download and run QuickHash.<br>
3. In QuickHash go to 'file' tab and select SHA256 as Hash Algorithm.<br>
4. Click 'Select File' and select the html file you just downloaded.<br>
5. A SHA256 HASH value will appear.<br>
6. Now go to bitaddress.org again, and at the bottom of the page click at the link to GitHub Repository.<br>
7. Once in their GitHub, click on the file 'CHANGELOG.txt'.<br>
8 At line 29 you will find
"bitaddress.org-v3.3.0-SHA256-dec17c07685e1870960903d8f58090475b25af946fe95a734f88408cef4aa194.html".<br>
9. Do the "dec17c07685e1870960903d8f58090475b25af946fe95a734f88408cef4aa194" match with the SHA256 you got from QuickHash?<br>
10. If matched, then the HTML you dowloaded is valid and authentic, if not, then something sketchy is going on.</p>

CC BY-SA 3.0
2017-12-05T22:20:08.167Z
2017-12-05T22:20:08.167Z
Chak
<p>Suppose I want to download a copy of <a href="https://liteaddress.org" rel="nofollow noreferrer">https://liteaddress.org</a> in order to run it offline in a safe environment. Then how can I verify that the website hasn't been hacked? How can I verify that the downloaded copy is legitimate and not compromised?</p>

<p>The website explains this:</p>

<blockquote>
  <p>If you are familiar with PGP you can download this all-in-one HTML page and check that you have an authentic version from the author of this site by matching the SHA256 hash of this HTML with the SHA256 hash available in the signed version history document linked on the footer of this site.</p>
</blockquote>

<p>I have just started to read what PGP is because I don't know what PGP and SHA256 hash even are and how they work.</p>

<p>My knowledge of computers is very basic. I mean, I know how to use a computer, but PGP, SHA256, etc. are too technical for me.</p>

<p>Can someone explain to me step by step (assuming my knowledge regarding these topics is zero) how to verify the PGP signature of liteaddress.org?</p>

CC BY-SA 3.0
2017-12-05T21:17:23.390Z
Well it seems like the devs haven't updated the SHA256 for liteaddress.org since 2015-01-08, so every commits after that date cannot be verified.
Chak
CC BY-SA 3.0
2017-12-06T18:43:00.993Z
@Chak so, does this mean that the PGP signature of liteaddress.org can't be verified?
User X
CC BY-SA 3.0
2017-12-06T19:18:03.393Z
In this case SHA256 of liteaddress.org cannot be authenticated. PGP acts more like a verification of "messages/emails/text". I would say that downloading from their GitHub repository is more safe/secure than download liteaddress.org, either way we wont know if any of them are compromised. However I checked their last commits since 20/07/15, and found nothing malicious. So I will deem their GitHub repository as safe for now, as long it is used offline.
Chak
CC BY-SA 3.0
2017-12-06T19:51:56.153Z
@Chak thanks! And what's the difference between PGP and SHA256? And what is "commits"?
User X
CC BY-SA 3.0
2017-12-06T20:23:07.343Z
Well is a bit complicated hmmm....   Simply explained SHA256 is mostly used for hashing, while PGP is more an encryption algorithm. SHA256 is designed so that it's (almost)impossible to turn a hash back into its original string. PGP on the other hand can easily be reversed back into its original decrypted form if you have the public key.
Chak
CC BY-SA 3.0
2017-12-06T20:31:45.563Z
Commits are related to GitHub, for example when codes have been altered or new codes added, programmers have to "commit" it so the current contents get saved. Simply put, it is like clicking "save" after editing a document.
Chak
<wallet><litecoin><signature><paper-wallet><pgp>
How can I verify the PGP signature of https://liteaddress.org on Windows?
User X
# How can I verify the PGP signature of https://liteaddress.org on Windows?

(Asked by: username_0 on 2017-12-05)

Suppose I want to download a copy of <https://liteaddress.org> in order to run it offline in a safe environment. Then how can I verify that the website hasn't been hacked? How can I verify that the downloaded copy is legitimate and not compromised?

The website explains this:

> If you are familiar with PGP you can download this all-in-one HTML page and check that you have an authentic version from the author of this site by matching the SHA256 hash of this HTML with the SHA256 hash available in the signed version history document linked on the footer of this site.

I have just started to read what PGP is because I don't know what PGP and SHA256 hash even are and how they work.

My knowledge of computers is very basic. I mean, I know how to use a computer, but PGP, SHA256, etc. are too technical for me.

Can someone explain to me step by step (assuming my knowledge regarding these topics is zero) how to verify the PGP signature of liteaddress.org?

**Tags:** wallet, litecoin, signature, paper-wallet, pgp

> **Comments:**
> **username_1**: Well it seems like the devs haven't updated the SHA256 for liteaddress.org since 2015-01-08, so every commits after that date cannot be verified.  
> **username_0**: @username_1 so, does this mean that the PGP signature of liteaddress.org can't be verified?  
> **username_1**: In this case SHA256 of liteaddress.org cannot be authenticated. PGP acts more like a verification of "messages/emails/text". I would say that downloading from their GitHub repository is more safe/secure than download liteaddress.org, either way we wont know if any of them are compromised. However I checked their last commits since 20/07/15, and found nothing malicious. So I will deem their GitHub repository as safe for now, as long it is used offline.  
> **username_0**: @username_1 thanks! And what's the difference between PGP and SHA256? And what is "commits"?  
> **username_1**: Well is a bit complicated hmmm....   Simply explained SHA256 is mostly used for hashing, while PGP is more an encryption algorithm. SHA256 is designed so that it's (almost)impossible to turn a hash back into its original string. PGP on the other hand can easily be reversed back into its original decrypted form if you have the public key.  
> **username_1**: Commits are related to GitHub, for example when codes have been altered or new codes added, programmers have to "commit" it so the current contents get saved. Simply put, it is like clicking "save" after editing a document.  

---

## 1 answers

### Answer by username_1 on 2017-12-05. Score: 1 | Accepted answer

These steps can be simplified if you use UNIX, as most of the tools are already available. However I assume you use Windows.
For PGP explanation, search for videos on youtube.

These steps are for the webpage bitaddress.org.

For the PGP part:  
1. Download and install Gpg4win.  
2. Go to bitaddress.org and click on the link at the bottom to go to Github Repsitory.  
3. On their Github page, click on 'CHANGELOG.txt.asc', then click on the 'raw' tab.  
4. Right-click and save as.  
5. Run Kleopatra(Gpg4win).  
6. Click on Decrypt/Verify tab.  
7. Find the CHANGELOG file you just downloaded and 'open'.  
8. Now click on the 'search' tab, since you are missing the public key to verify the message.  
9. The public key for ninja should have been found, click to import it.  
10. Click OK/YES when asked to certify the fingerprints, we know it is the correct ones since the key fingerprint is posted on <https://bitcointalk.org/index.php?topic=43496.0> .  
11. You will be asked to create a account, click yes.  
12. Type whatever you want(not important).  
13. Create a simple password.  
14. Click 'finish'.  
15. Select all the IDs, and then tick the box ' I have verified the fingerprint'and next.  
16. Click certify.  
17. Enter the password you just created.  
18. You will get certification successfull, click finish.  
19. Now you will be shown if the contents inside CHANGELOG is valid.  
20. If you get "The signature is valid and the certificate's validity is fully trusted." Then we know that the file content is authentic and hasn't been tampered with.  
21. So now we know that the file CHANGELOG.txt.asc inside their Github is authentic. We can process to the SHA256 part.

For the SHA256 part:  
1. Go to bitaddress.org and right-click and save as 'Webpage HTML only'  
2. Download and run QuickHash.  
3. In QuickHash go to 'file' tab and select SHA256 as Hash Algorithm.  
4. Click 'Select File' and select the html file you just downloaded.  
5. A SHA256 HASH value will appear.  
6. Now go to bitaddress.org again, and at the bottom of the page click at the link to GitHub Repository.  
7. Once in their GitHub, click on the file 'CHANGELOG.txt'.  
8 At line 29 you will find
"bitaddress.org-v3.3.0-SHA256-dec17c07685e1870960903d8f58090475b25af946fe95a734f88408cef4aa194.html".  
9. Do the "dec17c07685e1870960903d8f58090475b25af946fe95a734f88408cef4aa194" match with the SHA256 you got from QuickHash?  
10. If matched, then the HTML you dowloaded is valid and authentic, if not, then something sketchy is going on.


---

