[Bug]: Native SSH connection closed while other sessions are open

[Calvario]

Bug Description

Hello,

The scenario below was working as expected in version (1.37.22), but after upgrading to the latest version (1.49.12), the behavior changed.
While using “hoop cli” with hoop connect on a client PC to establish an SSH connection via the native SSH client, opening more than one SSH session through the same local SSH tunnel causes an issue: if one of the sessions is disconnected, both SSH sessions are terminated.

Regards.

Steps to Reproduce

Case 1 (the auto-created session + SCP connection)

• Open "hoop connect resource_name_ssh"
  <<
  INFO resource_name_ssh 🔒: proxy started, ready to accept connections at 127.0.0.1:2223
  INFO resource_name_ssh 🔒: /usr/bin/ssh 127.0.0.1 -p 2223 -o StrictHostKeyChecking=no

• The auto connected session is opened, I can do for example a "top" and keep it open.
• On a new window, I open FileZilla or WinSCP to upload a file to "127.0.0.1:2223"
• After sending the file, I disconnect my session on FileZilla / WinSCP.
• The "hoop connect resource_name_ssh" stop with
  <<
  INFO resource_name_ssh 🔒: ssh client disconnected

• The issue is that I was using the "auto connected session" / another SSH connection was still open and killed by the SSH SCP disconnect.

Case 2 (the auto-created session + another normal SSH connection)
Same as case 1 but using on another window: "/usr/bin/ssh 127.0.0.1 -p 2223 -o StrictHostKeyChecking=no"

Expected Behavior

The local "tunnel"/proxy should only disconnect if all sessions to it are closed to avoid killing open sessions that did not sent a "close".

Actual Behavior

If any session send a "close", all sessions connected to the tunnel/proxy are killed with it.

Version

1.49.12

Browser(s)

Chrome

Operating System

MacOS and Windows

Screenshots

No response

Additional Context

No response

Relevant Log Output

Code of Conduct

• I agree to follow this project's Code of Conduct