# 9E

This certificate and its associated private key is used to support additional physical access applications, such as providing physical access to buildings via PIV-enabled door locks. The main purpose of the slot 9E key is for physical access to restricted areas.

{% hint style="info" %} <mark style="color:yellow;">**PIN POLICY:**</mark>\
\
PIN is not required.\
PIN policy can only be changed for a slot if PIV certificate imported using ykman command-line.
{% endhint %}

{% hint style="info" %}
The instructions on this page are used for the tutorials ![](https://4238369593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqj0swE9RiXnBGKcxMY3V%2Fuploads%2Fy8eADDDxBD8nZlyw8MMc%2Flink_1.png?alt=media\&token=0eefc560-f6f2-464e-9a58-8d86df1fca61) [**Bitlocker**](https://app.gitbook.com/s/FqFACNHWgp8HSNubDNCu/tutorials/bitlocker) and ![](https://4238369593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqj0swE9RiXnBGKcxMY3V%2Fuploads%2Fy8eADDDxBD8nZlyw8MMc%2Flink_1.png?alt=media\&token=0eefc560-f6f2-464e-9a58-8d86df1fca61) [**EFS**](https://app.gitbook.com/s/FqFACNHWgp8HSNubDNCu/tutorials/efs)
{% endhint %}

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.&#x20;

<table><thead><tr><th width="136">SLOT</th><th>PIN Policy</th></tr></thead><tbody><tr><td><mark style="color:red;"><strong><code>9D</code></strong></mark></td><td>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.</td></tr><tr><td><mark style="color:red;"><strong><code>9E</code></strong></mark></td><td>The end user PIN is NOT required to perform private key operations for this slot.</td></tr></tbody></table>

To create a certificate to populate this slot, view the [**Bitlocker tutorial**](https://yubico.gitbook.io/yubikey5/piv-1/slots/broken-reference).

## <mark style="color:red;">❊ Distinguished Name Values</mark>

In the code below, you may edit the values in the <mark style="color:red;">**`[ yubikey_dn ]`**</mark> section and specify your own values. For a list of references about the abbresviations below, please review the ![](https://4238369593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqj0swE9RiXnBGKcxMY3V%2Fuploads%2Fy8eADDDxBD8nZlyw8MMc%2Flink_1.png?alt=media\&token=0eefc560-f6f2-464e-9a58-8d86df1fca61) [**Distinguished Name**](https://yubico.gitbook.io/yubikey5/piv-1/generate/with-openssl/distinguished_name) list.

## <mark style="color:red;">❊ Create OpenSSL Config</mark>

Copy the following config file to \ <mark style="color:yellow;">`C:\Program Files\Common Files\SSL\piv_slot_9e.cnf`</mark>

```properties
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

[ req ]

default_bits        = 2048
default_keyfile     = piv_sign_9e.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      = email@address.com
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 Card Authentication 9E"
subjectAltName      = @sans
extendedKeyUsage    = critical,msEFS, msEFSR, nsSGC, msEFSRecovery, driveEncryption, driveRecovery, msSmartcardLogin
keyUsage            = critical,keyEncipherment, dataEncipherment
```

{% hint style="warning" %}
If you are creating a PIV certificate specifically for Digital Signatures, don't change anything in the <mark style="color:red;">**`[ yubikey_extensions ]`**</mark> block.
{% endhint %}

{% hint style="info" %}
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 <mark style="color:red;">`piv_name_9e_priv`</mark>

<mark style="color:red;">`Priv`</mark> = Private key\ <mark style="color:red;">`Pub`</mark>  = Public key\
\ <mark style="color:red;">**`9E`**</mark> signifies the Yubikey PIV slot we'll be importing our certificate into.
{% endhint %}

## <mark style="color:red;">❊ Setup</mark>

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:

* [📁](https://emojipedia.org/file-folder/) private
* [📁](https://emojipedia.org/file-folder/) public
* [📁](https://emojipedia.org/file-folder/) openssh

## <mark style="color:red;">❊ Generate Key + Cert from Config</mark>

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

<table><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><mark style="color:red;"><strong><code>-new</code></strong></mark></td><td>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. <br><br>If <mark style="color:red;"><strong><code>-key</code></strong></mark> option not used, it will generate a new RSA private key using information specified in the configuration file.</td></tr><tr><td><mark style="color:red;"><strong><code>-x509</code></strong></mark></td><td>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.<br><br>If existing request is specified with the -in option, it is converted to the self signed certificate otherwise new request is created.</td></tr><tr><td><mark style="color:red;"><strong><code>-sha256</code></strong></mark></td><td><p>Specifies digest to sign the request with (such as -md5, -sha1). </p><p>Some public key algorithms may override this choice. Such as DSA signatures always use SHA1.</p></td></tr><tr><td><mark style="color:red;"><strong><code>-days</code></strong></mark></td><td>Requires <mark style="color:red;"><strong><code>-x509</code></strong></mark> . Specifies number of days to certify for. The default is 30 days.</td></tr><tr><td><mark style="color:red;"><strong><code>-config</code></strong></mark></td><td>Load alternative config. Oerrides the compile time filename or any specified in the OPENSSL_CONF environment variable.</td></tr><tr><td><mark style="color:red;"><strong><code>-keyout</code></strong></mark></td><td>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.</td></tr><tr><td><mark style="color:red;"><strong><code>-out</code></strong></mark></td><td>The output filename to write to or standard output by default.</td></tr></tbody></table>

```
openssl req -new -x509 -sha256 -days 1825 -config "C:\Program Files\Common Files\SSL\piv_name_9e.cnf" -keyout "private/piv_name_9e_priv.key" -out "public/piv_name_9e_pub.crt"
```

## <mark style="color:red;">❊ Create PFX</mark>

Merge your new private key and certificate together into a <mark style="color:red;">**`.pfx`**</mark>&#x20;

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

{% hint style="warning" %}
Keep this file safe. and away from others.&#x20;
{% endhint %}

<table data-header-hidden><thead><tr><th width="175"></th><th></th></tr></thead><tbody><tr><td><mark style="color:red;"><strong><code>-export</code></strong></mark></td><td>Specifies that a PKCS#12 file will be created rather than parsed.</td></tr><tr><td><mark style="color:red;"><strong><code>-in</code></strong></mark></td><td>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.</td></tr><tr><td><mark style="color:red;"><strong><code>-inkey</code></strong></mark></td><td>File to read private key from. If not present then a private key must be present in the input file.</td></tr><tr><td><mark style="color:red;"><strong><code>-out</code></strong></mark></td><td>Specifies filename to write the PKCS#12 file to. Standard output is used by default.</td></tr></tbody></table>

```
openssl pkcs12 -export -in "public/piv_name_9e_pub.crt" -inkey "private/piv_name_9e_priv.key" -out "private/piv_name_9e_priv.pfx"
```

## <mark style="color:red;">❊ Create Private + Cert (.PEM)</mark>

<table><thead><tr><th width="173"></th><th></th></tr></thead><tbody><tr><td><mark style="color:red;"><code>-in</code></mark></td><td>This specifies filename of the PKCS#12 file to be parsed. Standard input is used by default.</td></tr><tr><td><mark style="color:red;"><strong><code>-nodes</code></strong></mark></td><td>Stands for "No DES"<br>don't encrypt the private keys at all.</td></tr><tr><td><mark style="color:red;"><strong><code>-out</code></strong></mark></td><td>The filename to write certificates and private keys to, standard output by default. They are all written in PEM format.</td></tr></tbody></table>

{% tabs %}
{% tab title="Encrypted" %}

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

{% endtab %}

{% tab title="Unencrypted" %}

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

{% endtab %}
{% endtabs %}

## <mark style="color:red;">❊ Create Private Key (.KEY)</mark>

{% hint style="warning" %}
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.
{% endhint %}

{% tabs %}
{% tab title="Private | Encrypted" %}

## <mark style="color:red;">❊ Create Private Key \[Encrypted]</mark>

The following can generate a private <mark style="color:red;">**`encrypted`**</mark> key from your PFX file.

<table data-header-hidden><thead><tr><th width="161"></th><th></th></tr></thead><tbody><tr><td><mark style="color:red;"><code>-in</code></mark></td><td>This specifies filename of the PKCS#12 file to be parsed. Standard input is used by default.</td></tr><tr><td><mark style="color:red;"><strong><code>-out</code></strong></mark></td><td>The filename to write certificates and private keys to, standard output by default. They are all written in PEM format.</td></tr><tr><td><mark style="color:red;"><strong><code>-nocerts</code></strong></mark></td><td>No certificates at all will be output.</td></tr></tbody></table>

```
openssl pkcs12 -in "private/piv_name_9e_priv.pfx" -nocerts -out "private/piv_name_9e_enc_priv.key"
```

{% endtab %}

{% tab title="Private | Unencrypted" %}

## <mark style="color:red;">❊ Create Private Key \[Not Encrypted]</mark>

The following can generate a private <mark style="color:blue;">**`unencrypted`**</mark> key from your PFX file.

<table data-header-hidden><thead><tr><th width="161"></th><th></th></tr></thead><tbody><tr><td><mark style="color:red;"><code>-in</code></mark></td><td>This specifies filename of the PKCS#12 file to be parsed. Standard input is used by default.</td></tr><tr><td><mark style="color:red;"><strong><code>-out</code></strong></mark></td><td>The filename to write certificates and private keys to, standard output by default. They are all written in PEM format.</td></tr><tr><td><mark style="color:red;"><strong><code>-nocerts</code></strong></mark></td><td>No certificates at all will be output.</td></tr><tr><td><mark style="color:red;"><strong><code>-nodes</code></strong></mark></td><td>Stands for "No DES"<br>don't encrypt the private keys at all.</td></tr></tbody></table>

```
openssl pkcs12 -in "private/piv_name_9e_priv.pfx" -nocerts -nodes -out "private/piv_name_9e_unc_priv.key"
```

{% endtab %}
{% endtabs %}

## <mark style="color:red;">❊ Create OpenSSH (.PUB)</mark>

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 <mark style="color:red;">**`Security`**</mark> tab, and make sure <mark style="color:red;">**`Inheritance`**</mark> is disabled.

<table data-header-hidden><thead><tr><th width="117"></th><th></th></tr></thead><tbody><tr><td><mark style="color:red;"><strong><code>-y</code></strong></mark></td><td>This option will read a private OpenSSH format file and print an OpenSSH public key to stdout.</td></tr><tr><td><mark style="color:red;"><strong><code>-f</code></strong></mark></td><td>Specifies the filename of the key file.</td></tr></tbody></table>

```
ssh-keygen -y -f "private/piv_name_9e_priv.pem" > "openssh/piv_name_9e_openssh.pub"
```

## <mark style="color:red;">❊ Create Private RSA (.PEM)</mark>

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

```
openssl rsa -in "private/piv_name_9e_priv.pem" -out "private/piv_name_9e_priv_rsa.pem" -outform PEM -traditional
```

## <mark style="color:red;">❊ Create Public Certificate (.PEM)</mark>

Export public cert / key (PEM):

<table><thead><tr><th width="176"></th><th></th></tr></thead><tbody><tr><td><mark style="color:red;"><code>-in</code></mark></td><td>This specifies filename of the PKCS#12 file to be parsed. Standard input is used by default.</td></tr><tr><td><mark style="color:red;"><strong><code>-out</code></strong></mark></td><td>The filename to write certificates and private keys to, standard output by default. They are all written in PEM format.</td></tr><tr><td><mark style="color:red;"><strong><code>-nokeys</code></strong></mark></td><td>No private keys will be output.</td></tr><tr><td><mark style="color:red;"><strong><code>-clcerts</code></strong></mark></td><td>Only output client certificates (not CA certificates).</td></tr></tbody></table>

```
openssl pkcs12 -in "private/piv_name_9e_priv.pfx" -clcerts -nokeys -out "public/piv_name_9e_pub.pem"
```

## <mark style="color:red;">❊ Create Public Key</mark>

Export public key (RSA):

```
openssl rsa -in "private/piv_name_9e_priv.pem" -pubout > "public/piv_name_9e_pub.pub"
```