Verify
Before start using the GUI, it's strongly recommended to verify the authenticity of the krux-installer.SHA256.txt file. It attest the integrity of all variants (krux_installer_0.0.21_amd64.deb, krux_installer-0.0.21-1.x86_64.rpm, krux_installer_0.0.21_arm64.dmg, krux_installer_v0.0.21_Setup.exe).
To do this, download two files:
Verify the authenticity¶
Linux/MacOS
The next step is import the developer's key:
gpg --keyserver hkps://keys.openpgp.org --recv-keys B4281DDDFBBD207BFA4113138974C90299326322
Then, to verify yourself, run this:
gpg --verify krux-installer.SHA256.txt.sig
Windows
After install, you can proceed with Linux/MacOS steps in the terminal.
⚠️ TIP: If the verification was successful, you may get a message similar to:
Good signature from "qlrddev <qlrddev@gmail.com>". Also, you can ignore a WARNING message if it says that the key isn't a trusted one (you need to do it manually).
Verify the integrity¶
After verify that the krux-installer.SHA256.txt
is authentic, we can proceed with the integrity check in your bash/zsh terminal:
Linux / MacOS
sha256sum --check krux-installer.SHA256.txt
Windows
You can verify the integrity with this command in a powershell terminal:
$exe = '.\krux_installer_v0.0.21_Setup.exe'
$file = Split-Path $exe -Leaf
(Get-FileHash $exe -Algorithm SHA256).Hash -eq
(Select-String $file '.\krux-installer.SHA256.txt').Line.Split()[0].ToUpper()
🛡️ TIP: If you followed the authenticity/integrity checks steps presented, you already have the assurance that the software is from a verified and genuine software publisher. This will also help establish a chain of trust when you perform the firmware verification step before flashing.