⭕9D

PIV: Key Management

This certificate and its associated private key is used for encryption for the purpose of confidentiality. This slot is used for things like encrypting e-mails or files. The main purpose of the slot 9D key is to encrypt files or drives using EFS or Bitlocker Encryption.

PIN POLICY: PIN must be provided to perform any private key operations. PIN can be cached / remembered for a short period of time. PIN policy can only be changed for a slot if PIV certificate imported using ykman command-line.

The instructions on this page are used for the tutorials Bitlocker and EFS.

The difference between using slot 9D and 9E for encryption is that each slot has different PIN policies in place. You can manually change the pin policies for a slot if you import the PIV certificate using ykman. Currently, the Yubikey Manager does not allow PIN policies to be modified.

SLOT	PIN Policy
9D	The end user PIN is required to perform any private key operations. Once the PIN has been provided successfully, multiple private key operations may be performed without additional cardholder consent.
9E	The end user PIN is NOT required to perform private key operations for this slot.

❊ Distinguished Name Values

In the code below, you may edit the values in the [ yubikey_dn ] section and specify your own values. For a list of references about the abbresviations below, please review the Distinguished Name list.

❊ Create OpenSSL Config

Copy the following config file to C:\Program Files\Common Files\SSL\piv_slot_9d.cnf

oid_section         = yubikey_oids

[ yubikey_oids ]
nameDistinguisher   = 0.2.262.1.10.7.20
msEFSR              = 1.3.6.1.4.1.311.10.3.4.1
msEFSRecovery       = 1.3.6.1.4.1.311.21.6
driveEncryption     = 1.3.6.1.4.1.311.67.1.1
driveRecovery       = 1.3.6.1.4.1.311.67.1.2
rda                 = 1.3.6.1.4.1.311.54.1.2
gpgUsageCert        = 1.3.6.1.4.1.11591.2.6.1
gpgUsageSign        = 1.3.6.1.4.1.11591.2.6.2
gpgUsageEncr        = 1.3.6.1.4.1.11591.2.6.3
gpgUsageAuth        = 1.3.6.1.4.1.11591.2.6.4
msAuthenticode      = 1.3.6.1.4.1.311.2

[ req ]

default_bits        = 2048
default_keyfile     = piv_sign_9d.pem
default_md          = sha256
distinguished_name  = yubikey_dn
x509_extensions     = yubikey_ext
req_extensions      = yubikey_ext
string_mask         = MASK:0x2002
utf8                = yes
prompt              = no

[ yubikey_dn ]
0.C                 = NA
1.S                 = NA
2.L                 = NA
3.O                 = Organization
4.OU                = Organization Unit
5.CN                = Your Common Name
6.emailAddress      = [e-mail]
7.GN                = Your Given Name
8.title             = Cert Title
9.description       = Description about Cert
10.initials         = ABC
11.serialNumber     = 1234

[ sans ]
DNS.0               = localhost
DNS.1               = myexampleclient.com

[ yubikey_ext ]
basicConstraints    = CA:false,pathlen:0
nsCertType          = objsign, objCA
nsComment           = "PIV Authentication 9D"
subjectAltName      = @sans
extendedKeyUsage    = critical,serverAuth, clientAuth, emailProtection, msSGC, msEFS, msEFSR, nsSGC, msEFSRecovery, driveEncryption, driveRecovery, msSmartcardLogin, secureShellClient, secureShellServer, rda, gpgUsageCert, gpgUsageSign, gpgUsageEncr, gpgUsageAuth, msAuthenticode
keyUsage            = critical,nonRepudiation, keyEncipherment, dataEncipherment, keyAgreement

If you are creating a PIV certificate specifically for Digital Signatures, don't change anything in the [ yubikey_extensions ] block.

In the commands below, make sure to change the filenames and parameters to your own. In our examples, we like to name the files after the slot we're going to import them into on the yubikey such as piv_name_9d_priv

Priv = Private key Pub = Public key 9D signifies the Yubikey PIV slot we'll be importing our certificate into.

❊ Setup

Before getting started, create you a new folder where you will run all these commands and setup the following structure by creating the following files all in the same directory:

• 📁 private
• 📁 public
• 📁 openssh

❊ Generate Key + Cert from Config

An OpenSSL cert + private key can be generated using the following command:

-new	Generates new certificate request. Prompts user for the relevant field values. The actual fields prompted for and their maximum and minimum sizes are specified in config file. If -key option not used, it will generate a new RSA private key using information specified in the configuration file.
-x509	Outputs self signed certificate instead of certificate request. Unless specified using the set_serial option, a large random number will be used for the serial number. If existing request is specified with the -in option, it is converted to the self signed certificate otherwise new request is created.
-sha256	Specifies digest to sign the request with (such as -md5, -sha1). Some public key algorithms may override this choice. Such as DSA signatures always use SHA1.
-days	Requires -x509 . Specifies number of days to certify for. The default is 30 days.
-config	Load alternative config. Oerrides the compile time filename or any specified in the OPENSSL_CONF environment variable.
-keyout	Gives the filename to write the newly created private key to. If this option is not specified then the filename present in the configuration file is used.
-out	The output filename to write to or standard output by default.

openssl req -new -x509 -sha256 -days 1825 -config "C:\Program Files\Common Files\SSL\piv_name_9d.cnf" -keyout "private/piv_name_9d_priv.key" -out "public/piv_name_9d_pub.crt"

❊ Create PFX

Merge your new private key and certificate together into a .pfx

You will be prompted to provide a passphrase to execute the file.

Keep this file safe. and away from others.

-export	Specifies that a PKCS#12 file will be created rather than parsed.
-in	Filename to read certificates and private keys from. Must all be in PEM format. The order doesn't matter but one private key and its corresponding certificate should be present. If additional certificates are present they will also be included in the PKCS#12 file.
-inkey	File to read private key from. If not present then a private key must be present in the input file.
-out	Specifies filename to write the PKCS#12 file to. Standard output is used by default.

openssl pkcs12 -export -in "public/piv_name_9d_pub.crt" -inkey "private/piv_name_9d_priv.key" -out "private/piv_name_9d_priv.pfx"

❊ Create Private + Cert (.PEM)

-in	This specifies filename of the PKCS#12 file to be parsed. Standard input is used by default.
-nodes	Stands for "No DES" don't encrypt the private keys at all.
-out	The filename to write certificates and private keys to, standard output by default. They are all written in PEM format.

Encrypted

openssl pkcs12 -in "private/piv_name_9d_priv.pfx" -aes-256-cbc -out "private/piv_name_9d_priv.pem"

Unencrypted

openssl pkcs12 -in "private/piv_name_9d_priv.pfx" -nodes -out "private/piv_name_9d_priv.pem"

❊ Create Private Key (.KEY)

You can skip the steps for Create Private Key, this was done in the first command. These are here in case you need to create more.

Private | Encrypted

The following can generate a private encrypted key from your PFX file.

-in	This specifies filename of the PKCS#12 file to be parsed. Standard input is used by default.
-out	The filename to write certificates and private keys to, standard output by default. They are all written in PEM format.
-nocerts	No certificates at all will be output.

openssl pkcs12 -in "private/piv_name_9d_priv.pfx" -nocerts -out "private/piv_name_9d_enc_priv.key"

Private | Unencrypted

The following can generate a private unencrypted key from your PFX file.

-in	This specifies filename of the PKCS#12 file to be parsed. Standard input is used by default.
-out	The filename to write certificates and private keys to, standard output by default. They are all written in PEM format.
-nocerts	No certificates at all will be output.
-nodes	Stands for "No DES" don't encrypt the private keys at all.

openssl pkcs12 -in "private/piv_name_9d_priv.pfx" -nocerts -nodes -out "private/piv_name_9d_unc_priv.key"

❊ Create OpenSSH (.PUB)

To generate your OpenSSH key, you must ensure that the permissions on your pem file are properly set. This means that you must right-click on this file, go to the Security tab, and make sure Inheritance is disabled.

-y	This option will read a private OpenSSH format file and print an OpenSSH public key to stdout.
-f	Specifies the filename of the key file.

ssh-keygen -y -f "private/piv_name_9d_priv.pem" > "openssh/piv_name_9d_openssh.pub"

❊ Create Private RSA (.PEM)

Export private RSA key which can be used for connecting to SSH via Filezilla:

openssl rsa -in "private/piv_name_9d_priv.pem" -out "private/piv_name_9d_priv_rsa.pem" -outform PEM -traditional

❊ Create Public Certificate (.PEM)

Export public cert / key (PEM):

-in	This specifies filename of the PKCS#12 file to be parsed. Standard input is used by default.
-out	The filename to write certificates and private keys to, standard output by default. They are all written in PEM format.
-nokeys	No private keys will be output.
-clcerts	Only output client certificates (not CA certificates).

openssl pkcs12 -in "private/piv_name_9d_priv.pfx" -clcerts -nokeys -out "public/piv_name_9d_pub.pem"

❊ Create Public Key

Export public key (RSA):

openssl rsa -in "private/piv_name_9d_priv.pem" -pubout > "public/piv_name_9d_pub.pub"

❊ Import to Windows User Certificates

Click -> Run

Type certmgr. msc

Navigate to Certificates -> Current User -> Personal -> Certificates

In the white space, right-click and select All Tasks -> Import.

For Store Location select Current User and click Next.

Select the Browse button.

In the bottom right corner, click the dropdown and select Personal Information Exchange (*.pfx;*.p12) and select your recently exported piv_name_9d_priv.pfx

Select Next:

Enter the password you defined when you exported your PFX file with the openssl command.

Select Mark this key as exportable if you want to do a final export from the User Certificates list. If you do not select this option, you will not be able to export it later if you lose your openssl copies.

On the next window, it will ask where you wish to import the certificate to. I import to two locations:

You will need to import twice, to both the following locations:

• Certificates -> Current User -> Personal -> Certificates

• Certificates -> Current User -> Trusted Root Certification Authorities -> Certificates

Once you've completed the import:

Click Yes and you will finish the import:

You will need to go through the import process again to install your certificate in the other specified folders from above.

After completing the above steps, you should have the following files. You may delete the files you do not want, but ensure you leave at least one private key, one public, and the certificate. Also leave the OpenSSH public key if you wish to use this PIV slot to authenticate with SSH.

piv_name_9d_priv.pfx	Private key + certificate (password protected)
piv_name_9d_priv.pem	Private encrypted key + certificate
piv_name_9d_priv.key	Private encrypted key only
piv_name_9d_pub.pem	Public Certificate (pem format)
piv_name_9d_pub.crt	Public Certificate
piv_name_9d_openssh.pub	Public OpenSSH key