Hello Devolutions Team,
I would like to report a reproducible issue with YubiKey PIV authentication over SSH in Remote Desktop Manager for Linux.
The same YubiKey, PKCS#11 module, private key, and SSH server work correctly with native OpenSSH on Ubuntu. However, RDM terminates the connection immediately after entering the PIV PIN, while the YubiKey is still waiting for physical touch confirmation.
I have performed extensive testing to isolate the problem.
1. Environment
Client:
Operating system: Ubuntu 24.04 LTS
Architecture: x86_64
Desktop environment: GNOME
Display server: X11
Remote Desktop Manager: 2026.3.2.1 (64-bit)
OpenSSH: 9.6p1
OpenSC: 0.25.0~rc1-1ubuntu0.2
PKCS#11 library: /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
YubiKey Manager CLI: 5.2.1
Hardware security key:
Model: YubiKey 5C NFC
Firmware: 5.7.4
Application: PIV
PIV slot: 9A (PIV Authentication)
Algorithm: ECC P-256
Key generated directly on the YubiKey
PIN policy: ALWAYS
Touch policy: ALWAYS
Self-signed X.509 certificate: CN=YubiKey-SSH
Private key: Hardware-resident and non-exportable
SSH server:
Debian Linux virtual machine on a local network
OpenSSH server
Public-key authentication enabled
Password authentication enabled
AuthenticationMethods any
YubiKey public key installed in the user's ~/.ssh/authorized_keys
The SSH server is functioning correctly and accepts the YubiKey public key when using native OpenSSH.
2. OpenSC and PKCS#11 verification — SUCCESSFUL
OpenSC detects the YubiKey correctly.
Command:
pkcs11-tool \
--module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so \
--list-slots
Relevant output:
Slot 0: Yubico YubiKey OTP+FIDO+CCID
token label: YubiKey-SSH
token flags: login required, rng, token initialized, PIN initialized
The PIV authentication certificate is visible:
pkcs11-tool \
--module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so \
--list-objects \
--type cert
Output:
Certificate Object; type = X.509 cert
label: Certificate for PIV Authentication
subject: DN: CN=YubiKey-SSH
ID: 01
After entering the PIV PIN, OpenSC also detects the private key object:
pkcs11-tool \
--module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so \
--login \
--list-objects \
--type privkey
Output:
Private Key Object; EC
label: PIV AUTH key
ID: 01
Usage: sign
Access: sensitive, always sensitive, never extractable, local
This confirms that the existing PIV private key is available for signing operations through PKCS#11 without exporting private key material.
3. Independent ECDSA signing test — SUCCESSFUL
I performed a direct PKCS#11 ECDSA signing test using the existing key in PIV slot 9A.
The operation required:
Entering the PIV PIN.
Physically touching the YubiKey.
The operation successfully produced a 64-byte raw ECDSA signature.
After converting the signature to ASN.1 DER format, I verified it using OpenSSL and the corresponding public key.
Command:
openssl pkeyutl -verify \
-pubin \
-inkey "$HOME/yubikey_ssh_9a_public.pem" \
-sigfile "$HOME/yubikey_piv_test/signature.der" \
-in "$HOME/yubikey_piv_test/digest.bin"
Result:
Signature Verified Successfully
Therefore, ECDSA signing through OpenSC works correctly with the hardware-protected key, including PIN and touch enforcement.
4. Native OpenSSH authentication — SUCCESSFUL
The same YubiKey successfully authenticates to the Debian SSH server using the native Ubuntu OpenSSH client.
Command:
ssh \
-o PKCS11Provider=/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so \
-o PreferredAuthentications=publickey \
-o PasswordAuthentication=no \
-o KbdInteractiveAuthentication=no \
<SSH_USER>@<DEBIAN_TEST_VM>
Observed behavior:
OpenSSH requests the YubiKey PIV PIN.
I enter the PIN.
The YubiKey indicates that physical touch is required.
I touch the YubiKey.
Public-key authentication succeeds.
The Debian SSH shell opens normally.
I have successfully repeated this test multiple times.
Password and keyboard-interactive authentication are explicitly disabled for these tests, so the successful connection cannot be attributed to password fallback.
The Debian SSH logs confirm successful public-key authentication:
Accepted publickey for <SSH_USER> from <CLIENT_IP>
ssh2: ECDSA SHA256:<REDACTED_PUBLIC_KEY_FINGERPRINT>
Followed by:
pam_unix(sshd:session): session opened for user <SSH_USER>
Native OpenSSH authentication works reliably with this exact YubiKey and PKCS#11 module.
5. Remote Desktop Manager configuration
I created a separate SSH Shell test connection in RDM.
Configuration:
Connection type: SSH Shell
Host: <DEBIAN_TEST_VM>
Username: <SSH_USER>
Password: Empty
Use smart card: Enabled
Certificate method: PKCS
PIN code: Empty
SSH key → Private key: No private key
Algorithm support: Default
Use SSH authentication agent: Disabled
Display error messages: Default (Yes)
The PIN field is intentionally empty because I do not want to store the security key's PIN in the application.
In the RDM application settings, the Smart Card PKCS library is configured as:
/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
I verified that the RDM process actually loads this library:
sudo lsof -nP | grep -F 'opensc-pkcs11.so'
Relevant output:
RemoteDes ... <LOCAL_USER> ... /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
Therefore, RDM loads the correct OpenSC PKCS#11 library.
I also disconnected my second hardware security key during testing, leaving only the YubiKey 5C NFC available to OpenSC.
6. RDM SSH authentication — FAILURE
Steps to reproduce:
Connect the YubiKey 5C NFC.
Start Remote Desktop Manager 2026.3.2.1 on Ubuntu 24.04.
Open the SSH Shell test connection.
RDM displays a PIV PIN prompt.
Enter the correct PIV PIN.
Actual behavior:
Immediately after entering the PIN:
The PIN prompt disappears.
RDM terminates the SSH connection attempt.
The interface returns to the connection's Overview screen.
No terminal session opens.
No visible error message is displayed.
The YubiKey remains illuminated, apparently waiting for physical touch confirmation.
Touching the YubiKey turns off the light, but RDM does not resume the connection.
This behavior is reproducible.
The key observation is that RDM abandons the SSH connection while the YubiKey is still indicating that physical interaction is required.
The YubiKey does not show exactly the same LED behavior as during a successful native OpenSSH authentication.
I understand that the LED behavior alone does not prove the cause, but the disconnect timing is consistent.
7. Debian SSH server logs during failed RDM authentication
I monitored the SSH server logs during a single controlled RDM connection attempt:
sudo journalctl -u ssh -f -o short-iso
The server recorded:
sshd[<PID>]: Connection closed by authenticating user <SSH_USER> <CLIENT_IP> port <PORT> [preauth]
There was no corresponding Accepted publickey message for that controlled RDM attempt.
The connection therefore ended before SSH authentication completed.
By contrast, native OpenSSH attempts produce successful Accepted publickey events followed by the opening of a user session.
8. Troubleshooting already performed
Connection logging
I enabled:
Enable logging: Yes
Log path type: Custom
Log mode: Event
Verbose: 4
Log into terminal: No
The custom log file was not created during the failed authentication attempts.
Launching RDM from an Ubuntu terminal
I started RDM using:
remotedesktopmanager 2>&1 | tee "$HOME/rdm-piv-console.log"
The output file was created successfully but remained empty after reproducing the issue.
RDM Application logs
I opened:
Help → Application logs
I enabled all available log types:
Error
Error silent
Info
Only informational messages relating to a local database upgrade were displayed.
There were no relevant SSH, PKCS#11, ECDSA, or smart-card authentication errors.
RDM System diagnostics
I checked:
Help → System diagnostics
Relevant information:
Ubuntu 24.04
Architecture: X64
Desktop environment: GNOME
Display server: X11
Container: None
Debug level: 1
The report did not identify the SSH authentication failure.
SSH algorithm configuration
I inspected RDM's Algorithm support settings.
The available categories were:
Cipher
Host key
Kex
MAC
ECDSA SHA2 NIST P-256 is available in the host-key algorithm list.
I left Algorithm support set to Default because host-key algorithms are distinct from client public-key authentication algorithms.
9. Expected behavior
I expect RDM to:
Load the configured OpenSC PKCS#11 module.
Use the existing ECC P-256 PIV Authentication key in slot 9A.
Request the PIV PIN.
Wait for physical touch confirmation without terminating the SSH connection.
Complete ECDSA signing using the private key on the YubiKey.
Complete SSH public-key authentication.
Open the SSH terminal session.
This exact authentication flow works with native OpenSSH.
10. Questions for the Devolutions development team
Could you please clarify the following?
1. Is SSH authentication using YubiKey PIV through OpenSC PKCS#11 officially supported in Remote Desktop Manager 2026.3.2.1 for Linux?
2. Does this implementation support ECC P-256 PIV keys configured with both PIN ALWAYS and TOUCH ALWAYS?
3. Is there a known issue where the SSH connection closes immediately after entering the PIV PIN while the hardware token is still waiting for physical touch?
4. Could the behavior be related to the handling of blocking PKCS#11 signing operations, touch confirmation, a timeout, or an asynchronous signing issue?
5. Is CKM_ECDSA signing through OpenSC supported in this SSH authentication scenario?
6. Is the following configuration correct for a hardware-resident PIV key?
Use smart card: Enabled
Certificate method: PKCS
Private key: No private key
PIN code: Empty
7. Can RDM on Linux use native OpenSSH or an external OpenSSH SSH agent for PKCS#11-backed SSH authentication instead of its internal smart-card implementation?
8. How can detailed SSH authentication and PKCS#11 signing diagnostics be enabled in the Linux application?
9. Is this a known issue, and is there a fix, workaround, or newer build that addresses it?
I would strongly prefer a solution that preserves the existing security policies:
PIN ALWAYS
TOUCH ALWAYS
I do not want to export or locally store the private key or weaken the hardware authentication requirements.
11. Summary
WORKING:
Ubuntu OpenSSH
→ OpenSC PKCS#11
→ YubiKey 5C NFC / PIV 9A
→ PIV PIN
→ Physical touch
→ ECC P-256 ECDSA signature
→ Successful Debian SSH authentication
FAILING:
Remote Desktop Manager 2026.3.2.1
→ OpenSC PKCS#11 library loaded
→ YubiKey PIV PIN requested
→ Correct PIN entered
→ SSH connection immediately closes
→ YubiKey remains illuminated awaiting touch
→ SSH authentication does not complete
Because the same hardware token, private key, PKCS#11 module, and SSH server work successfully through native OpenSSH, I suspect an issue in RDM's Linux SSH/PKCS#11 authentication flow.
I would appreciate confirmation of the supported configuration and guidance on diagnosing or resolving this behavior.
Thank you for your assistance.