Possible regression: YubiKey PKCS#11 ECDSA signing on Linux

Possible regression: YubiKey PKCS#11 ECDSA signing on Linux

avatar

RDM 2026.3.1.2, Devolutions.ProtocolsSharp 2026.9.28.2 fails with:

SSH session: Failed to initiate PKCS11 ECDSA signing

Provider: /usr/lib/x86_64-linux-gnu/libykcs11.so

Explicit PKCS#11 certificate method also fails. The YubiKey starts blinking.

OpenSSH with ssh -vvv -I /usr/lib/x86_64-linux-gnu/libykcs11.so user@host prompts for PIN and authenticates successfully.

The same setup worked in an older RDM version.

Linux distribution: Ubuntu 24.04.5 LTS

All Comments (5)

avatar

Hello Stanislav,

Thank you for the detailed report and for testing with OpenSSH. Since the same YubiKey and libykcs11.so work with the native client, the token and the library themselves look fine. I need a few details to narrow down what RDM is doing differently.

1. Which RDM Linux version was the last one where this setup worked, and how did you install RDM (DEB package, Flatpak or something else)?

2. In RDM, open the settings under Application > Paths. Which value is set in "Smart card PKCS library"? Is it /usr/lib/x86_64-linux-gnu/libykcs11.so, or still the default (opensc-pkcs11)?

3. Which type of key does the YubiKey provide? This command lists the public keys exposed by the library, with their type (for example ssh-rsa or ecdsa-sha2-nistp256):

  ssh-keygen -D /usr/lib/x86_64-linux-gnu/libykcs11.so

  Please send me the output. It contains public keys only, so it is safe to share. If the command asks for your PIN, please just tell me, and do not include the PIN in your reply.

4. How is the SSH entry configured? Please tell me:

  - whether "Use smart card" is enabled and whether a PIN is saved in the entry

  - whether a private key or certificate is also set in the entry

  - whether "Use SSH authentication agent" is enabled in the Advanced tab

5. Please send the session log with the highest detail:

  - In the SSH entry, open the Logs tab, enable logging, set "Log path type" to Custom, enter a full path in your home folder such as /home/<your user>/rdm-ssh.log, and set Verbose to 4.

  - Connect once so that the error appears.

  - Send me the log file. Please make sure your PIN does not appear in it.

6. If you can, also send the output of your working command with the extra detail, so we can compare what OpenSSH offers and signs with what RDM does:

  ssh -vvv -I /usr/lib/x86_64-linux-gnu/libykcs11.so user@host

I will review everything as soon as I receive it. I cannot confirm yet whether this is a defect in RDM, so I do not want to promise a fix before we understand the cause.

Best regards,

Alexis Geller Peiro

avatar

Ad 1) 2025.2.1.5 (I still install RDM from DEB)

Ad 2) /usr/lib/x86_64-linux-gnu/libykcs11.so

Ad 3) ssh-rsa A**************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************D Public key for PIV Authentication

Ad 4)

 - 'Use smart card' is enabled, regarding PIN, I have tried both to set it in entry, and to set it manually, when asked for it during authentication process

 - private key or certificate is NOT set in the entry

 - 'Use SSH authentication agent' is not enabled

Ad 5) log records:

[11/12/2026 4:23:35 PM] Devolutions.ProtocolsSharp: 2026.9.28.2 OS: Linux

[11/12/2026 4:23:35 PM] SSH session: Failed to initiate PKCS11 ECDSA signing

avatar

Hi Stanislav,

Thank you for the details.

We were able to reproduce this behavior in our lab, and it is now logged as a bug that our development team is working on. Your answers are very useful: they show that the issue also happens with an RSA key and with the Yubico libykcs11.so library, whether the PIN is saved in the entry or typed at the prompt, and that it worked in 2025.2.1.5. I added all of this to the bug.

In the meantime, please keep using the native OpenSSH client with libykcs11.so, which works on your side. I also recommend not using smart card authentication in RDM until the fix is available: in our tests, when a wrong PIN was entered, RDM kept retrying the login, and on a YubiKey this could use up the PIV PIN retries and block the PIN.

I will let you know as soon as a version with the fix is available.

Best regards,

Alexis Geller Peiro

avatar

Ad 1) 2025.2.1.5 (I still install RDM from DEB)

Ad 2) /usr/lib/x86_64-linux-gnu/libykcs11.so

Ad 3) ssh-rsa A**************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************D Public key for PIV Authentication

Ad 4)

 - 'Use smart card' is enabled, regarding PIN, I have tried both to set it in entry, and to set it manually, when asked for it during authentication process

 - private key or certificate is NOT set in the entry

 - 'Use SSH authentication agent' is not enabled

Ad 5) log records:

[11/12/2026 4:23:35 PM] Devolutions.ProtocolsSharp: 2026.9.28.2 OS: Linux

[11/12/2026 4:23:35 PM] SSH session: Failed to initiate PKCS11 ECDSA signing

@stanislavmotycka

Native OpenSSH successfully authenticates using the same PKCS#11 provider as RDM: /usr/lib/x86_64-linux-gnu/libykcs11.so, with the SSH agent disabled (IdentityAgent=none).

The successful sequence is: PIV PIN → YubiKey blinks → touch → server account password → login.

In RDM, after entering the PIV PIN, the YubiKey does not start blinking for touch. The SSH tab closes immediately with Failed to initiate PKCS11 ECDSA signing (ProtocolsSharp 2026.9.28.2, Linux).

USB OTP is disabled and PIV remains enabled. The server requires both public-key and password authentication.

avatar

Hi Stanislav,

Thank you for the additional details, I added them to the bug report. I will let you know as soon as we have any news.

Best regards,

Alexis Geller Peiro