-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
OpenSSH Connections hang on exiting because authentication channel is not closed #3784
Comments
@tcannonfodder Do you have SSH agent forwarding enabled? I think this is a bug that was introduced in #3613 (which was backported to Teleport 4.2.9). We're currently working on a fix via #3741. If you're curious about a workaround for now, you could downgrade your Teleport proxy server to a Teleport version <=4.2.8, or disable SSH agent forwarding if you don't require it. |
@webvictim I do have agent forwarding enabled. I can wait for a fix, thankfully this is more an annoyance than a showstopper. :) |
I just encountered a similar bug with port forwarding using openssh client: $ ssh -L 8080:google.com:443 talos.root
% # use the tunnel via a browser
% <ctrl-d>
# hangs
<ctrl-c> # this actually closes the connection
$ ( Curiously, this does not happen if no connections are made over the forwarded port. So, something about the connection lingers and prevents SSH from closing. Server logs:
|
👋 @awly I just hit the same issue, did you find any workarounds? Do you know if this is a known OpenSSH issue? Would appreciate any pointers :) |
FYI the port forwarding behaviour may be expected: https://serverfault.com/a/20715/217299 From ssh man:
|
@ravwojdyla I have not looked into this issue since that last comment. |
Description
What happened:
When connecting to a server using OpenSSH, the SSH connection is not completely closed when exiting the connection. When debugging, it looks like the initial connection to the teleport Auth Service is not closed
What you expected to happen:
All SSH connections (including the one created by the
ProxyJump
should be closed automaticallyHow to reproduce it (as minimally and precisely as possible):
I'm not entirely sure. I just updated Teleport to 4.2.10 and encountered this issue.
Environment
SSH version:
OpenSSH_8.1p1, LibreSSL 2.7.3
Teleport version:
Teleport v4.2.10 git: go1.14.3
Tsh version:
Teleport v4.2.9 git: go1.14.3
OS: MacOS for the client, Ubuntu LTS 20.04 for the auth server, Ubuntu 16.04 for the node server
Where are you running Teleport? (e.g. AWS, GCP, Dedicated Hardware):
VPS instances
Relevant Debug Logs If Applicable
Below is a snippet of the debug output from SSH when I run the following command:
The text was updated successfully, but these errors were encountered: