# Preparar env en Debian 13

En linux disponemos de unas herramientas para sacar partido a las llave Yubikey.<br>

<figure><img src="/files/aWrKouSmJhIqTTf3CGAw" alt=""><figcaption></figcaption></figure>

**📦 Instalación de paquetes:**

```bash
sudo apt install -y gnupg2 scdaemon yubikey-manager pcscd pcsc-tools libccid
```

Habilitamos el servicio

```bash
sudo systemctl enable --now pcscd
```

output:

```bash
Synchronizing state of pcscd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable pcscd
Created symlink '/etc/systemd/system/sockets.target.wants/pcscd.socket' → '/usr/lib/systemd/system/pcscd.socket'.
```

\
Comprobamos que se está ejecutando:

```bash
systemctl status pcscd
```

output:

```bash
● pcscd.service - PC/SC Smart Card Daemon
     Loaded: loaded (/usr/lib/systemd/system/pcscd.service; indirect; preset: enabled)
     Active: active (running) since Thu 2025-12-11 13:39:51 CET; 5s ago
 Invocation: 38a214155ba9490c89f78196ebe85bb8
TriggeredBy: ● pcscd.socket
       Docs: man:pcscd(8)
   Main PID: 5074 (pcscd)
      Tasks: 5 (limit: 76857)
     Memory: 2.2M (peak: 2.9M)
        CPU: 71ms
     CGroup: /system.slice/pcscd.service
             └─5074 /usr/sbin/pcscd --foreground --auto-exit
```

🔑 **Conectamos la Yubikey al equipo, y si ha ido bien veremo información de nuestra llave:**

```bash
ykman info
```

output:

```bash
Device type: YubiKey 5C NFC
Serial number: ********
Firmware version: 5.7.4
Form factor: Keychain (USB-C)
Enabled USB interfaces: OTP, FIDO, CCID
NFC transport is enabled

Applications	USB    	NFC    
Yubico OTP  	Enabled	Enabled
FIDO U2F    	Enabled	Enabled
FIDO2       	Enabled	Enabled
OATH        	Enabled	Enabled
PIV         	Enabled	Enabled
OpenPGP     	Enabled	Enabled
YubiHSM Auth	Enabled	Enabled
```

✅ 🎉 Bien!!! te detecta la llave perfectamente!

**⚙️ Personalización**

```bash
gpg --card-status
```

output:

```bash
Reader ...........: Yubico YubiKey OTP FIDO CCID 00 00
Application ID ...: D********************************
Application type .: OpenPGP
Version ..........: 3.4
Manufacturer .....: Yubico
Serial number ....: ********
Name of cardholder: [no establecido]
Language prefs ...: [no establecido]
Salutation .......: 
URL of public key : [no establecido]
Login data .......: [no establecido]
Signature PIN ....: no forzado
Key attributes ...: rsa2048 rsa2048 rsa2048
Max. PIN lengths .: 127 127 127
PIN retry counter : 3 0 3
Signature counter : 0
KDF setting ......: off
UIF setting ......: Sign=off Decrypt=off Auth=off
Signature key ....: [none]
Encryption key....: [none]
Authentication key: [none]
General key info..: [none]
```

Si has llegado a este punto y no has tenido problemas, tienes lo necesario para administrar la llave en Linux.

{% hint style="danger" %}
Es posible que te de problemas gpg --card-status
{% endhint %}

Si al ejecutar:

```bash
gpg --card-status
```

Te sale este output:

```bash
gpg: selecting card failed: Service is not running
gpg: tarjeta OpenPGP no disponible: Service is not running
```

Ejecuta:

```bash
gpgconf --kill gpg-agent
gpgconf --launch gpg-agent
gpg --card-status
```

y ya deberia solucionar el problema.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://blog.azagra.dev/yubikey/preparar-env-en-debian-13.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.