# Verify Kicksecure ™ Virtual Machine Images in Windows

#### Your support makesall the difference!

We believe security software like Kicksecure needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 10 year success story and maybe DONATE!

# Introduction

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:

1. Install SignTool.
4. Verify the Kicksecure ™ images.

# Verify Kicksecure ™ Images in Windows using Gpg4win

## Install SignTools

The following instructions install SignTool in Windows 10 (stable release). For earlier Windows releases (Windows XP, Vista, 7 and 8) users can install SignTool by substituting the corresponding SDK Installer found in the Windows SDK archives for the Windows 10 SDK installer in the below instructions.

SignTools is a Windows command-line tool that uses Authenticode to digitally sign files and verify both signatures in files and time stamp files. SignTool is available as part of Mirosoft Windows SDK, which can be can be installed in just a few easy steps. Once installed it can be used to verify the gpg4win package before installation.

• Right-click Downloading The InstallerRight-click SaveRight-click Run.

2. Set the correct path.

• Right-click Continuechoose PATHC:\Users\<user_name>\Downloads\Windows Kits\<windows_version>\WindowsSDKRight-click Next.

Figure: Choose SDK Installation Path

3. Install the necessary SDK package.

The Windows SDK installer provides a number of different packages that can be installed. The only package needed for gpg4win verification is Windows SDK Signing Tools for Desktop Apps (SignTools). Be mindful that earlier SDK version packages may be named differently from later SDK versions. For example, the package that contains SignTool in SDK for Windows 8.1 is named Windows Software Developmental Kit. This differs from the corresponding package in Windows 10.

Figure: Select SignTools Package

Once the box to the corresponding package is "checked", right-click Download. Once installation is complete, close the installer.

SignTool can be used to verify the authenticity of the gpg4win package itself.

Note: To simplify the SignTool verification process be sure to download the gpg4win package to the Downloads directory.

1. Download the gpg4win package.

• Navigate to https://files.gpg4win.org
• Scroll down and download the latest version of gpg4win and the corresponding signature. At the time of writing (August 2020) gpg4win-3.1.12.exe was the latest version.
• Since the Intevation CA certificate has been imported, no errors should be encountered when the gpg4win package is downloaded.

2. Verify the gpg4win package by running SignTool from the command prompt.

To open a command prompt, in the Windows Start Menu, run.

cmd.exe

Verify the gpg4win package using SignTool.

signtool verify /pa gpg4win-3-1.12.exe

The following output shows a successful gpg4win verification.

Figure: Successful Verification

Warning: if verification fails, delete the gpg4win package and repeat the download and verification process again.

This entry is strongly related to the Placing Trust in Kicksecure ™ page.

This entry is for Download the Kicksecure ™ Signing Key on the Windows platform. Includes Windows specifics such as file paths. This chapter might be out of date. In case of questions, see the Kicksecure Signing Key page first which takes presedence.

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 C:\Users\<user_name\Downloads

1. If not already completed, have GnuPG initialize your user data folder.

gpg --fingerprint

Error in widget Key_Patrick: Unable to load template 'wiki:Key_Patrick'

Store the key as C:\Users\<user_name>\Downloads\derivative.asc

3. Change to the C:\Users\<user_name>\Downloads\ directory.

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. [2]

      Key fingerprint = 916B 8D99 C38E AF5E 8ADC  7A2A 8D66 066A 2EEA CCDA


The message gpg: key 8D66066A2EEACCDA: 104 signatures not checked due to missing keys is related to the The OpenPGP Web of Trust. Advanced users can learn more about this here.

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.

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.

cd C:\Users\<user_name>\<directory_name>

3. Verify the Whonix.ova image.

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 <adrelanos@whonix.org>" [unknown] gpg: Signature notation: issuer-fpr@notations.openpgp.fifthhorseman.net=6E979B28A6F37C43BE30AFA1CB8D50BB77BB3C48 gpg: Signature notation: file@name=Kicksecure-16.0.9.8.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.

Check the GPG signature timestamp makes sense. For example, if you previously saw a signature from 2020 and now see a signature from 2019, then this might be a targeted rollback (downgrade) or indefinite freeze attack. [3]

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


Note: OpenPGP signatures sign files, but not file names. [4]

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.

Do not continue if verification fails! This risks using infected or erroneous files! The whole point of verification is to confirm file integrity. This page is strongly related to the pages Placing Trust in Kicksecure ™ and Verifying Software Signatures.

4. When Kicksecure ™ verification is complete, continue with the VirtualBox installation.

# Troubleshooting

## SignTool is not Recognized

Figure: SignTool not Recognized Error

This error means the SignTool executable is not accessible through cmd.exe. A common cause for this error is SignTool was not installed in the user's PATH. To fix this issue add signtool.exe to your system PATH. [5]

Note: This solution is temporary and works only until the command prompt is closed. When the command prompt is restarted signtool.exe must be added to the system PATH again.

1. Open a command prompt.

In the Windows Start menu, run.

cmd.exe

2. Add the path to signtool.exe to your system PATH.

The default installation path for signtool.exe:

x86 systems:  C:\Program Files (x86)\Windows Kits\<windows_version>\bin\x86
x64 systems:  C:\Program Files (x86)\Windows Kits\<windows_version>\bin\x64


Run the following command to add "path\to\signtool.exe" to your system PATH. Also be sure to add the Windows version to the path.

set PATH="path to signtool.ext";%PATH%

For example, the following command adds the path for an x64 system.

set PATH="C:\Program Files (x86)\Windows Kits\<windows_version>\bin\x64";%PATH%

## SignTool Certificate Chain Error

Figure: Root Certificate Error

This error message occurs if the /pa switch is not used with SignTool. This is because the default SignTool verify some_file.exe command uses the Windows Driver Verification Policy. [6] In order for the file to verify properly the /pa switch must be used so SignTool uses the Default Authentication Verification Policy.

## 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.

# Footnotes

1. curl --tlsv1.3 --proto =https --max-time 180 --output derivative.asc https://www.whonix.org/derivative.asc
2. Minor changes in the output such as new uids (email addresses) or newer expiration dates are inconsequential.
3. As defined by TUF: Attacks and Weaknesses:
4. See stackoverflow for further information: Why's My Root Certificate Not Trusted?

Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.