All Collections
Security
Interface Validation
Verifying the Desktop App Authenticity
Verifying the Desktop App Authenticity
How to use the SHA256 checksums to verify the authenticity of the desktop application.
Lukas Schor avatar
Written by Lukas Schor
Updated over a week ago

For maximum security, it is recommended to verify the checksum after downloading the desktop app. This way, you can make sure that the executable file was not tampered with by a third-party.

1) Download the App

First, download the executable file for the desktop application and place it in a folder.

2) Verify Checksum

You can use this tool to verify the SHA256 checksum of the file. Alternatively you can manually verify the checksum using a terminal command.

Manually verifying the checksums differs depending on the operating system you use.

Linux

To hash the executable file on Linux, run the following command in a terminal:

$ sha256sum Safe-Multisig-APPVERSION.AppImage

Make sure to replace the filename (Safe-Multisig-APPVERSION.AppImage) with the actual filename of the file you downloaded. You should see the hash. Open the safe-global react Github repository and check if the hash matches with the one displayed for the this particular release.

MacOS

To hash the executable file on MacOS, run the following command in a terminal:

$ shasum -a 256 Safe-Multisig-APPVERSION.dmg

Make sure to replace the filename (Safe-Multisig-APPVERSION.dmg) with the actual filename of the file you downloaded. You should see the hash. Open the safe-global react Github repository and check if the hash matches with the one displayed for the this particular release.

Windows

To hash the executable file on Windows, run the following command in PowerShell:

> CertUtil -hashFile Safe-Multisig-Setup-APPVERSION.exe SHA256

Make sure to replace the filename (Safe-Multisig-Setup-APPVERSION.exe) with the actual filename of the file you downloaded. You should see "SHA256 hash of Safe-Multisig-Setup-APPVERSION.exe:" with the hash below. Open the safe-global react Github repository and check if the hash matches with the one displayed for the this particular release.


Did this answer your question?