ssh key forwarding (smart card login) crashes RDM

Implemented

ssh key forwarding (smart card login) crashes RDM

avatar

Hi,

I'm using RDM 2022.3.32.0 64 Bit RDM and a YubiKey to authenticate my ssh connections (with the WinCryptSSHAgent and the YubiKey Smartcard Minidriver). So far so good everything works fine.

But when I try to hop from one ssh connection to another with ssh key forwarding, then the RDM crashes and I have to restart the RDM. Not the thing I would expect.

Is there a possibility to use a YubiKey and still use ssh key forwarding? Is it just a bug of the version of the RDM?

Thanks

Patrick Hilke

All Comments (15)

avatar

Hello Patrick,

Thank you for reaching out to us regarding this,

I see, was this working for you without issues in a previous version of RDM?

Would it be possible for you to create a portable installation of the latest version of RDM and see if this issue still occurs? To do so, you will need to do the following:

1- Download the .zip file below:

https://remotedesktopmanager.com/home/thankyou/rdmbin

2- Create a new folder on your Desktop

3- Extract the content of the .zip file into the folder created at #2

4- Go to this folder once the .zip file has been extracted and run remotedesktopmanager.exe

5- Connect to your data source

Let me know,

Best regards,

Samuel Dery

avatar

Hello Samuel,

thank you for your response. My colleague who is the admin of the RDM installation creates a test installation with the newest version of RDM. I will test as soon as possible.

The installation requires a newer version of the database as well, so I cannot test it with the database version right now.

Best regards

Patrick

avatar

Hello Patrick,

Thank you for your reply,

No need to upgrade your database for this test, you can use a Local SQLite data source to confirm if you encounter the same behavior.

To create one simply go under "File" -> "Data source" and press the "Add new data source" (+) button, once done select SQLite and recreate your entry configuration.

Let me know the results.

Best regards,

Samuel Dery

avatar

I did that and got the same experience. The RDM crashed completely, meaning the whole window disappears and I have to restart the program.

Create ssh connection

set hostname

set username

enable "Use smartcard" with Certificate method CAPI

in Advanced Tab enable "Allow SSH authentication agent forwarding"

Log into the server with ssh

open another ssh session from there and during opening the RDM window dissapears

For authentication I used a YubiKey with the YubiKey Smart Card Minidriver 4.1 x64 and WinCrypt SSH Agent x64

avatar

Hello Patrick,

Thank you for your reply,

I see, do you have any logs from this crash directly in the application under "Help" -> "Application Logs"?

If not, could you have a look in your Windows event viewer and let me know if you find anything?

Best regards,

Samuel Dery

avatar

Hello,

I can confirm the same problem still exists with version 2023.3.32.0, both the fully installed version and the portable. When agent forwarding is enabled with CAPI smart card flag, the application crashes when jumping to a second host, or when querying if agent forwarding is enabled with a "ssh-add -L" command.

Any update here? Willing to test betas!!

Love the product otherwise,

Lee

avatar

Sorry for the late reply, was busy with other things.

I looked under "Help" -> "Application Logs", but it is nothing there.

I cleared all entry, let the application crash again and the log was still completely clean.

I translated the event log entrys from german:

Application Error:

Name of the faulty application: RemoteDesktopManager.exe, version: 2023.2.22.0, timestamp: 0xb02c0c7a

Name of the faulty module: unknown, version: 0.0.0.0, timestamp: 0x00000000

Exception code: 0xc0000005

Error offset: 0x0000000000000000

ID of the faulty process: 0x43e0

Start time of the faulty application: 0x01da2839941eab56

Path of the faulty application: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe

Path of the faulty module: unknown

Identifier report: 7d9bf2fc-de57-488c-898d-ee6f7f5cbf36

Full name of the faulty package:

Application ID that is relative to the faulty package:

ID: 1000

.Net Runtime Error:

Application: RemoteDesktopManager.exe

Framework version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception information: Exception code c0000005, exception address 0000000000000000

Stack:

ID: 1026

avatar

I have three Windows event log entries and one generic log entry within RemoteDesktopManager:

Windows Event log:

Log Name: Application

Source: Application Error

Date: 12/8/2023 9:37:39 AM

Event ID: 1000

Task Category: Application Crashing Events

Level: Error

Keywords:

User:

Computer:

Description:

Faulting application name: RemoteDesktopManager.exe, version: 2023.2.18.0, time stamp: 0x88ed67e2

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x0000000000000000

Faulting process id: 0x0x427C

Faulting application start time: 0x0x1DA29E44D90B8A0

Faulting application path: C:\Users\admin\OneDrive\devolutions\RemoteDesktopManager.exe

Faulting module path: unknown

Report Id: 3dff3c33-d633-4962-a0ec-7e29869e52c0

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />

<EventID>1000</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>100</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2023-12-08T15:37:39.7915343Z" />

<EventRecordID>3391</EventRecordID>

<Correlation />

<Execution ProcessID="4396" ThreadID="1220" />

<Channel>Application</Channel>

<Computer>-</Computer>

<Security UserID="" />

</System>

<EventData>

<Data Name="AppName">RemoteDesktopManager.exe</Data>

<Data Name="AppVersion">2023.2.18.0</Data>

<Data Name="AppTimeStamp">88ed67e2</Data>

<Data Name="ModuleName">unknown</Data>

<Data Name="ModuleVersion">0.0.0.0</Data>

<Data Name="ModuleTimeStamp">00000000</Data>

<Data Name="ExceptionCode">c0000005</Data>

<Data Name="FaultingOffset">0000000000000000</Data>

<Data Name="ProcessId">0x427c</Data>

<Data Name="ProcessCreationTime">0x1da29e44d90b8a0</Data>

<Data Name="AppPath">C:\Users\admin\OneDrive\devolutions\RemoteDesktopManager.exe</Data>

<Data Name="ModulePath">unknown</Data>

<Data Name="IntegratorReportId">3dff3c33-d633-4962-a0ec-7e29869e52c0</Data>

<Data Name="PackageFullName">

</Data>

<Data Name="PackageRelativeAppId">

</Data>

</EventData>

</Event>

Log Name: Application

Source: Windows Error Reporting

Date: 12/8/2023 9:37:45 AM

Event ID: 1001

Task Category: None

Level: Information

Keywords:

User: -\

Computer: -

Description:

Fault bucket 1728942364468260724, type 5

Event Name: BEX64

Response: Not available

Cab Id: 0

Problem signature:

P1: RemoteDesktopManager.exe

P2: 2023.2.18.0

P3: 88ed67e2

P4: StackHash_ac46

P5: 0.0.0.0

P6: 00000000

P7: PCH_EE_FROM_ntdll+0x000000000009FEC4

P8: c0000005

P9: 0000000000000008

P10:

Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6af1dbad-fec0-491c-90c4-34108be010d7.tmp.dmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.eaa1baab-575a-40f0-b5c6-05adb9e236fd.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c5ddc2f2-4ecb-4a31-b0c0-0c6db56500b6.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f1fc353e-0198-42c0-94a2-8d0938a81ef8.tmp.txt

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.22f15a53-bd4a-4e67-8f65-ff7436e6a2b2.tmp.xml

These files may be available here:

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_RemoteDesktopMan_ddf5a692636a65c9e09e35e7fc2ff5dab2ee1b7_1d944a02_68dff438-2c24-4031-8da4-9650f066f6b3

Analysis symbol:

Rechecking for solution: 0

Report Id: 3dff3c33-d633-4962-a0ec-7e29869e52c0

Report Status: 268435456

Hashed bucket: edfd3fae6a7e6a2097fe6feb8f412f74

Cab Guid: 0

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" />

<EventID>1001</EventID>

<Version>0</Version>

<Level>4</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2023-12-08T15:37:45.5053227Z" />

<EventRecordID>3392</EventRecordID>

<Correlation />

<Execution ProcessID="4396" ThreadID="1220" />

<Channel>Application</Channel>

<Computer>DESKTOP-GDVJU9V</Computer>

<Security UserID="" />

</System>

<EventData>

<Data Name="Bucket">1728942364468260724</Data>

<Data Name="BucketType">5</Data>

<Data Name="EventName">BEX64</Data>

<Data Name="Response">Not available</Data>

<Data Name="CabId">0</Data>

<Data Name="P1">RemoteDesktopManager.exe</Data>

<Data Name="P2">2023.2.18.0</Data>

<Data Name="P3">88ed67e2</Data>

<Data Name="P4">StackHash_ac46</Data>

<Data Name="P5">0.0.0.0</Data>

<Data Name="P6">00000000</Data>

<Data Name="P7">PCH_EE_FROM_ntdll+0x000000000009FEC4</Data>

<Data Name="P8">c0000005</Data>

<Data Name="P9">0000000000000008</Data>

<Data Name="P10">

</Data>

<Data Name="AttachedFiles">

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6af1dbad-fec0-491c-90c4-34108be010d7.tmp.dmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.eaa1baab-575a-40f0-b5c6-05adb9e236fd.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c5ddc2f2-4ecb-4a31-b0c0-0c6db56500b6.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f1fc353e-0198-42c0-94a2-8d0938a81ef8.tmp.txt

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.22f15a53-bd4a-4e67-8f65-ff7436e6a2b2.tmp.xml</Data>

<Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_RemoteDesktopMan_ddf5a692636a65c9e09e35e7fc2ff5dab2ee1b7_1d944a02_68dff438-2c24-4031-8da4-9650f066f6b3</Data>

<Data Name="AnalysisSymbol">

</Data>

<Data Name="Rechecking">0</Data>

<Data Name="ReportId">3dff3c33-d633-4962-a0ec-7e29869e52c0</Data>

<Data Name="ReportStatus">268435456</Data>

<Data Name="HashedBucket">edfd3fae6a7e6a2097fe6feb8f412f74</Data>

<Data Name="CabGuid">0</Data>

</EventData>

</Event>

Log Name: Application

Source: .NET Runtime

Date: 12/8/2023 9:37:39 AM

Event ID: 1026

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: -

Description:

Application: RemoteDesktopManager.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: exception code c0000005, exception address 0000000000000000

Stack:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name=".NET Runtime" />

<EventID Qualifiers="0">1026</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2023-12-08T15:37:39.4259898Z" />

<EventRecordID>3390</EventRecordID>

<Correlation />

<Execution ProcessID="17020" ThreadID="0" />

<Channel>Application</Channel>

<Computer>-</Computer>

<Security />

</System>

<EventData>

<Data>Application: RemoteDesktopManager.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: exception code c0000005, exception address 0000000000000000

Stack:

</Data>

</EventData>

</Event>

RDM:

An error occurred while sending a data source event: An error occurred while sending the request.

avatar

I can reproduce the bug, I will need to investigate it to give more details.

Regards

Denis Vincent

avatar

Still no update on this?

A workaround is to use a powershell window and do an:

ssh -A username@host

This works fine, but is is not working from within the RDM

avatar

Hello,

Are you encountering a crash of the application when performing smart card login? If so, could you try out the latest version of RDM? The fix for this has been available since 2023.3.34.0. If you encounter a different issue, we would need you to give us more information on the behavior, by way of sending us the application logs in RDM as well as the terminal logs (in the SSH shell entry, enable the logs, in verbose level 2, this will generate a file).

Regards,

Hubert Mireault

avatar

I will try the latest version next week, I am still on 2023.2.22.0

Thanks for the Update!

avatar

Hello Patrick,

Thank you for your reply,

No problem, let us know if the issue persists for you after updating.

Best regards,

Samuel Dery

avatar

I will do, but I have to wait for my RDM admin, he will deploy the newest version.

avatar

Hello,

Thank you for your reply,

No problem, I will wait for your return on this,

Best regards,

Samuel Dery