English Dutch
8d61f992a7e2dbc3d753470b4928b5bb9134ea14cf6f2973ba11d1600c0ce9ad
monero-linux-x64-v0.15.0.1.tar.bz2
``` 8d61f992a7e2dbc3d753470b4928b5bb9134ea14cf6f2973ba11d1600c0ce9ad monero-linux-x64-v0.15.0.1.tar.bz2 ```
Binary Verification on Linux or Mac ### 4.2. Binary verifiëren op Linux of Mac
Binary Verification on Windows ### 4.3. Binary verifiëren op Windows
``` certUtil -hashfile monero-gui-win-x64-v0.15.0.1.zip SHA256 ``` ``` certUtil -hashfile monero-gui-win-x64-v0.15.0.1.zip SHA256 ```
Download and Verify Binary ## 4. Binary downloaden en verifiëren
Download and Verify Hash File ## 3. Hashbestand downloaden en verifiëren
- [Download & Verify Binary](#download-and-verify-binary)
- [Download & Verify Hash File](#download-and-verify-hash-file)
From a terminal, get the `SHA256` hash of your downloaded Monero binary. As an example this guide will use the `Windows, 64bit` GUI binary. Substitute `monero-gui-win-x64-v0.15.0.1.zip` with the name of the binary that you downloaded in [section 4.1](#41-get-monero-binary). In een terminal bereken je de `SHA256`-hash van je gedownloade Monero-binary. Als voorbeeld gebruiken we hier het binaire bestand voor de 64-bits Windows GUI. Vervang `monero-gui-win-x64-v0.12.0.0.zip` door de naam van het binaire bestand dat je hebt gedownload in [paragraaf 4.1](#41-get-monero-binary).
From a terminal, import the signing key: Importeer de ondertekeningssleutel in een terminal:
Get Hash File ### 3.1. Hashbestand ophalen
Get Monero binary ### 4.1. Monero-binary ophalen
Get Signing Key ### 2.1. Ondertekeningssleutel ophalen
``` gpg --import binaryfate.asc ``` ``` gpg --import binaryfate.asc ```
gpg: key F0AF4D462A0BDF92: 2 signatures not checked due to missing keys
gpg: key F0AF4D462A0BDF92: public key "binaryFate <[email protected]>" imported
gpg: Total number processed: 1
gpg: imported: 1
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
```
gpg: key F0AF4D462A0BDF92: 2 signatures not checked due to missing keys
gpg: key F0AF4D462A0BDF92: public key "binaryFate <[email protected]>" imported
gpg: Total number processed: 1
gpg: imported: 1
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
```
gpg: key F0AF4D462A0BDF92: "binaryFate <[email protected]>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
```
gpg: key F0AF4D462A0BDF92: "binaryFate <[email protected]>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
```
``` gpg --keyid-format long --with-fingerprint binaryfate.asc ``` ``` gpg --keyid-format long --with-fingerprint binaryfate.asc ```
gpg: using RSA key 81AC591FE9C4B65C5806AFC3F0AF4D462A0BDF92
gpg: Good signature from "binaryFate <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 81AC 591F E9C4 B65C 5806 AFC3 F0AF 4D46 2A0B DF92
```
gpg: using RSA key 81AC591FE9C4B65C5806AFC3F0AF4D462A0BDF92
gpg: Good signature from "binaryFate <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 81AC 591F E9C4 B65C 5806 AFC3 F0AF 4D46 2A0B DF92
```
``` gpg --verify hashes.txt ``` ``` gpg --verify hashes.txt ```
If the file is authentic, the output will look like this: Als het bestand authentiek is, ziet de uitvoer er als volgt uit: