





Your code signing certificate could be kept secure and protected from hackers with the use of a YubiKey FIPS-compliant USB Token. Assuming you have a signing certificate in a .pfx format issued by a trustworthy certified certificate authority like Certera, Sectigo, or Comodo.
Let’s have a look at how to use Yubikey for Code Signing Certificate
If you are a Windows applications distributor or software developer, you are familiar with the significance of digitally signing certificates for your software. Such that a basic level of responsibility and trust could potentially be built between you and the consumers.
Additionally, you should know that this procedure is often carried out by obtaining a Windows Authenticode credential (a credential is a certificate plus its associated private key), which can subsequently be utilized to generate digital signatures for binary executables.
However, every individual additionally needs to know that if the signing security process provided the slightest chance, fraudulent people would make efforts to steal your code signing information which leads to unexplainable losses to the victim. If you’re a software developer, it requires just one malicious software to download for your authentication information and protective passwords to end up in the wrong hands.
Therefore, storing credentials on a disc is a highly dangerous decision, even if it is a portable USB drive you insert solely while signing binaries.
Therefore, you want to keep your login information on a specific, removable device that is perfectly made to secure that information. And that’s where the efficient and reasonably priced Yubico YubiKeys—come into action.
Prerequisite
We will utilize the “signtool.exe” to sign code on Windows operating systems. This function is distributed as a segment of the Windows SDK.
Use the https://go.microsoft.com/fwlink/p/?linkid=870807 link to install the SDK
The stages to import the certificate are based on whether you already have installed the YubiKey smart card mini driver.
If you’re unsure, check Device Manager’s Smart Cards section. If the smart card appears as “Yubico Yubikey,” it indicates that the driver is installed. However, if it appears as “NIST,” it means that the driver is not installed.
To enable the mini driver for importing certificates for code signing, follow these steps.
Nevertheless, you will be forced whenever you run singtool.exe – it’s unavoidable.
Without Mini driver
You can now sign the code with your installed code signing certificate on the YubiKey.
The SHA1 thumbprint is the most trustworthy method for assuring that the correct certificate is being utilized for signing. Follow the procedures below to obtain the thumbprint.
Note. The /t constraint is not obligatory (it is optional) and states the timestamp of the server server. It strongly stamps a digital signature, including time and date.
You have signed the executable file successfully with the certificate stored in the YubiKey. You can check the signature in the Digital Signature tab of the executable file properties.
Once importing of the key is done, again, there is a chance that the code signing failure. A quick and effective remediation for this is to disconnect and reconnect the Yubikey.
In conclusion, YubiKey is an effective tool for securing and protecting online accounts and code-signing certificates. In the steps explained above, software developers or distributors can guarantee the authenticity and integrity of signing code certificate credentials.
YubiKey is a security token that allows users to add a second factor of authentication to online services from vendors such as Google, Microsoft, Amazon, and Salesforce. The YubiKey, derived from the words ubiquitous key, looks like a USB stick.
The YubiKey code is nothing but a YubiKey passcode. The passcode is created by concatenating various YubiKey fields into a 128-bit long string and encrypting the string with the YubiKey configuration’s unique 128-bit AES key.
YubiKey authentication process:
YubiKey Version | Maximum Total Cert Space Available | Number of Certs at Size | Number of Certs at Maximum Size |
before 4.0 (e.g. NEO) | 8100 | 4 certs at 2025 bytes | 4 certs at 2025 bytes |
4.x | about 49,800 | 24 certs at 2075 bytes | 16 certs at 3052 bytes |
4.x FIPS | about 49,800 | 24 certs at 2075 bytes | 16 certs at 3052 bytes |
5.x | about 50,000 | 24 certs at 2084 bytes | 16 certs at 3052 bytes |
5.x FIPS | about 49,890 | 24 certs at 2079 bytes | 16 certs at 3052 bytes |
Owners can protect private keys with the YubiKey by importing them or, better yet, by generating a private key directly on the YubiKey. Private keys cannot be exported or extracted from YubiKey. YubiKey supports multiple methods to enable hardware-enabled SSH authentication.
To get your YubiKey certificate:
Open the YubiKey Manager GUI tool and connect the YubiKey to the computer. Click the Applications drop-down menu on the YubiKey Manager home page and select PIV. Under Certificates, select Configure Certificates.
Each YubiKey comes pre-loaded with a private key and certificates from Yubico that let in you generate an attestation certificate to confirm that a private key has been generated on a YubiKey.
The YubiKey FIPS series offers great data security and protection against social engineering activities like phishing and account hijacking. It enables various organizations and government agencies to meet the highest authentic security requirements. YubiKey FIPS provides strong one-touch authentication.