Installation

Downloading Kryptor

Pre-built binaries for Windows (x64), Linux (x64 and ARM64), and macOS (x64 and ARM64) are available on the Introduction page.

Kryptor is also available as a package from several package managers, although help is wanted to make it available elsewhere.

Building Kryptor from source

Downloading the source code

  1. Go to the latest release on GitHub and download the Source code (zip) asset.

  2. Navigate to the download location and extract the ZIP file.

Do NOT download the source code from the master branch.

Using the .NET CLI

  1. Install the latest .NET 8 SDK. This may be newer than the SDK and runtime version used to build the release files.

  2. Navigate to the src folder in the terminal (e.g. cd Downloads\Kryptor-4.0.0\src).

  3. Copy and paste the following command for the operating system and architecture you'd like to build for:

Windows (x64)

dotnet publish -c Release -r win-x64

The libsodium library requires the Visual C++ Redistributable for Visual Studio 2015-2022 to work on Windows. However, the appropriate vcruntime140.dll is automatically written to disk by Kryptor.

Linux (x64)

dotnet publish -c Release -r linux-x64

macOS (x64)

dotnet publish -c Release -r osx-x64

Linux (ARM64)

dotnet publish -c Release -r linux-arm64

macOS (ARM64)

dotnet publish -c Release -r osx-arm64

Publishing for osx-arm64 requires using macOS because Apple Silicon Macs require code signing.

Linux (ARM)

dotnet publish -c Release -r linux-arm

win-arm64 isn't supported yet. Currently, linux-arm, linux-arm64, linux-musl-arm64, and linux-musl-x64 are not tested. Better support and testing are on the roadmap.

A full list of .NET CLI publish options can be found here. The settings Kryptor uses can be found in the Kryptor.csproj file.

Verifying signatures

If you already have Kryptor installed, you can use the previous version to verify the .signature file for your new download.

If you don't have a previous version of Kryptor installed, you should follow the Verifying digests section below instead.

  1. Download the signature file for your version of Kryptor here.

  2. Make sure the .signature file is in the same directory as the downloaded Kryptor .zip file.

  3. Open the Command Prompt on Windows (e.g. search for cmd in the taskbar) or the terminal on Linux and macOS (e.g. search your programs for terminal).

  4. For v4 and above, copy and paste the following command, replacing [file] with the file path of the Kryptor .zip file:

kryptor -v -y Ed//bnY+xqUXVMaaI0poBwTqDRlKA9+x9FjlDAHE9MmXKG4= "[file]"

For v3, use the following command instead:

kryptor -v -y RWRudj7GpRdUxpojSmgHBOoNGUoD37H0WOUMAcT0yZcobg== "[file]"

Kryptor should display the message 'Good signature', followed by the authenticated comment 'Kryptor v[version]'.

If you see 'Bad signature', your download is either corrupted or not legitimate and may be unsafe.​

Verifying digests

Windows

  1. Download the latest SHA-256 .digest file here.

  2. Open a PowerShell window (e.g. search PowerShell in the taskbar).

  3. Navigate to the directory of the downloaded Kryptor .zip file (e.g. cd Downloads).

  4. Copy and paste the following command into PowerShell:

(Get-FileHash .\kryptor-windows-x64.zip).Hash -eq (Get-Content .\kryptor-windows-x64.zip.digest).split(" ")[0].ToUpper()

The word True should appear in the PowerShell window.

If you see False, your download is either corrupted or not legitimate and may be unsafe.​

Linux and macOS

  1. Download the latest SHA-256 .digest file here.

  2. Open a terminal window (e.g. search your programs for terminal).

  3. Navigate to the directory of the downloaded Kryptor .zip file (e.g. cd Downloads).

  4. Copy and paste the following command, replacing [file] with the file name of the .zip file:

shasum -a 256 -c [file].digest

The word OK should appear.

If you see another message, your download is either corrupted or not legitimate and may be unsafe.​

Last updated