Verify Kicksecure Virtual Machine Images in Windows
Instructions for OpenPGP Verification of Kicksecure Images using Windows
- Digital signatures: A tool enhancing download security. Commonly used across the internet.
- Learn more: Curious? Learn more about digital software signatures.
- Optional: Digital signatures are optional. If you've never used them before, there might be no need to start now.
- No worries: New to digital software signatures? It's okay, no need to worry.
- Not a requirement: Not mandatory for using Kicksecure, but an extra security measure for advanced users.
GnuPG is a complete and free implementation of OpenPGP that allows users to encrypt and sign data and communications. Gpg4win is a graphical front end for GnuPG that is used for file and email encryption in Windows. The verification process for the Kicksecure images begins with securely downloading and verifying the
gpg4win package. Once completed GPG can be used from the command-line to verify the Kicksecure images.
The following guide provides steps to:
- Install SignTool.
- Download and verify GPG4win.
- Download the Kicksecure signing key.
- Verify the Kicksecure images.
Verify Kicksecure Images in Windows using Gpg4win
Download and Verify Gpg4win
1. Prerequisite: SignTool
Before proceeding, ensure you have
SignTool installed. It's used to verify the authenticity of the
gpg4win package. For installation instructions, refer to Authenticode - Windows Digital Software Signatures chapter Install SignTool.
2. Download the
- Visit https://files.gpg4win.org.
- Find and download the most recent version of
gpg4winand its corresponding signature. (As of August 2020, the latest version was
- Tip: To simplify the SignTool verification, download the
gpg4winpackage directly to the Downloads directory.
3. Verify the Package using SignTool:
Open the command prompt from the Windows Start Menu:
Change to the Downloads directory:
Run SignTool to verify the
signtool verify /pa gpg4win-3-1.12.exe
Upon successful verification, the following output will appear:
Figure: Successful Verification
You've successfully verified the Gpg4win package.
Download the Kicksecure Signing Key
Since all Kicksecure releases are signed with the same key, it is unnecessary to verify the key every time a new release is announced. Trust in the key might gradually increase over time, but cryptographic signatures must still be verified every time a new release is downloaded.
Note: With the exception of step 1 all commands should be run from
1. If not already completed, have GnuPG initialize your user data folder.
Store the key as
3. Change to the
4. Check fingerprints/owners without importing anything.
gpg --keyid-format long --with-fingerprint derivative.asc
5. Verify the output.
The most important check is confirming the key fingerprint exactly matches the output below. 
Key fingerprint = 916B 8D99 C38E AF5E 8ADC 7A2A 8D66 066A 2EEA CCDA
6. Import the key.
gpg --import derivative.asc
The output should include the key was imported.
gpg: Total number processed: 1 gpg: imported: 1
If the Kicksecure signing key was already imported in the past, the output should include the key is unchanged.
gpg: Total number processed: 1 gpg: unchanged: 1
If the following message appears at the end of the output.
gpg: no ultimately trusted keys found
This extra message does not relate to the Kicksecure signing key itself, but instead usually means the user has not created an OpenPGP key yet, which is of no importance when verifying virtual machine images.
Analyze the other messages as usual.
Verify the Kicksecure Images
1. If not already completed, download both
Whonix.ova images and the corresponding OpenGPG signature which will be used to verify the image.
Both the signature and .ova image should be downloaded into the same directory.
- Download the Kicksecure VM image and signature from VirtualBox Table; or
- Download the Kicksecure VM Image and Signature from VirtualBox Table.
2. Start the cryptographic verification; this process can take several minutes.
At the Windows command prompt, change to the directory with the
Whonix.ova and corresponding signature file.
3. Verify the
gpg --verify-options show-notations --verify Whonix*.ova.asc Whonix*.ova
If the Virtual Machine image is correct the output will tell you that the signature is good.
gpg: Signature made Mon 19 Jan 2015 11:45:41 PM CET using RSA key ID 77BB3C48 gpg: Good signature from "Patrick Schleizer <email@example.com>" [unknown] gpg: Signature notation: firstname.lastname@example.org=6E979B28A6F37C43BE30AFA1CB8D50BB77BB3C48 gpg: Signature notation: file@name=Kicksecure-184.108.40.206.ova 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: 916B 8D99 C38E AF5E 8ADC 7A2A 8D66 066A 2EEA CCDA Subkey fingerprint: 6E97 9B28 A6F3 7C43 BE30 AFA1 CB8D 50BB 77BB 3C48
This might be followed by a warning saying:
gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner.
This message does not alter the validity of the signature related to the downloaded key. Rather, this warning refers to the level of trust placed in the Kicksecure signing key and the web of trust. To remove this warning, the Kicksecure signing key must be personally signed with your own key.
The first line includes the signature creation timestamp. Example.
gpg: Signature made Mon 19 Jan 2015 11:45:41 PM CET using RSA key ID 77BB3C48
To help users confirm that the file name has not been tampered with, beginning with Kicksecure version 9.6 and above the file@name OpenPGP notation includes the file name.
4. When Kicksecure verification is complete, continue with the VirtualBox installation.
Encountering GPG Errors
When a GPG error is encountered, first try a web search for the relevant error. The security stackexchange website can also help to resolve GPG problems. Describe the problem thoroughly, but be sure it is GPG-related and not specific to Kicksecure.
More help resources are available on the Support page.
- curl --tlsv1.3 --proto =https --max-time 180 --output derivative.asc https://www.whonix.org/derivative.asc
- Minor changes in the output such as new uids (email addresses) or newer expiration dates are inconsequential.
- As defined by TUF: Attacks and Weaknesses: