Knowledge base
1000 FAQs, 500 tutorials and instructional videos. Here, there are only solutions!
Verify the integrity of the kDrive installer (Checksum)
This guide explains how to verify the integrity and authenticity of the kDrive installer by comparing its digital fingerprint (checksum) with the one provided on the Infomaniak download page.
Introduction
- When you download the kDrive desktop application (Windows, macOS, or Linux), you can verify that the file has not been corrupted or altered during the transfer using a SHA256 checksum.
- The digital signature (SHA256 fingerprint) for each installer is available on the download page.
Check the checksum of your file
On Windows
You don't need to install any third-party software; use the built-in certutil utility via the command prompt:
- Open the Start menu and type
cmdto open the command prompt. - Access the folder where the installer is located (e.g.,
cd Downloads). - Type the following command (replace kDrive.exe with the actual name of the downloaded file):
certutil -hashfile kDrive.exe SHA256
On macOS
Use the terminal built into macOS:
- Open the Terminal (via Spotlight or in Applications > Utilities).
- Type the following command, followed by a space, then drag and drop the downloaded file into the terminal window:
shasum -a 256
Example result: shasum -a 256 kDrive.dmg
On Linux
Most Linux distributions include the sha256sum tool:
- Open your terminal.
- Run the following command:
sha256sum kDrive.deb (or .rpm / .AppImage)
Interpreting the result
Once the command has been executed, a string of characters (letters and numbers) will be displayed. Compare this string with the one displayed on Infomaniak:
- The codes are identical: the file is authentic and complete; you can proceed with the installation safely.
- The codes are different: the file is likely corrupted or has been modified; it is recommended to delete the file and restart the download from your Infomaniak interface.
For Linux users who use the official repositories (.deb), the verification is generally handled automatically by your package manager via the repository signature.
Link to this FAQ: https://faq.infomaniak.com/457
Has this FAQ been helpful?