-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSH port forwarding leaks connections after exit #8097
Comments
Could someone at least either confirm this bug or tell me what I'm doing wrong? |
I'm having the same issue. In fact, just using |
I stopped using tabby after a few days of reporting this. It doesn't seem to follow any security considerations and if bugs like this one remain open for months, this isn't the standard for apps I install on my work laptop. The fact that it has like 1.7k issues open isn't a good sign. Good luck. |
@TheQuantumPhysicist I'm sure you'll be happy to donate some of your time to work on this issue or help triage existing tickets to this open-source project run by a single person in their free time. |
Hey @Eugeny, thanks for investing so much time on Tabby. For now I've worked around this issue by removing the hotkey from |
Two points, since we're bordering on being rude
And I'm trying to be respectful here. So let's play nice. You ignored a security issue for months. This isn't a good look. |
@ExpLog this is not the case of having another open tab connected to the same server or using the same server as a jump host, right? Since the underlying session and its port forwards is shared between tabs. |
@Eugeny it doesn't look like it, since I'm seeing it happen with empty shells. To add some context I'm running zsh under WSL2 on Windows 11. My steps to reproduce:
That being said, I think it has definitely also happened the way you described. Thanks for the help, by the way, I appreciate it. |
Thanks @Eugeny! I appreciate it (: |
When calling
ssh somehostname -L1234:127.0.0.1:1234
(for port forwarding) from a tabby terminal, closing the terminal (CMD+Q) doesn't abort the tunnel connections.I use bash as the default terminal on MacOS 13.2.1.
The text was updated successfully, but these errors were encountered: