- Notifications
You must be signed in to change notification settings - Fork927
feat(agent/agentssh): use tcp for X11 forwarding#14560
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
9d3f404
to8fdf92f
Compare8fdf92f
tof6f2964
CompareUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Nothing else blocking on my end!
8f07d33
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
This PR changes X11 forwarding from socket-based to TCP based. This matches OpenSSH behavior where theclient forwards from
/tmp/.X11-unix/X*
and the server listens onlocalhost:6000(+)
.Since we can now have multiple SSH connections that each handle their individual X11 forwarding, we can end up adding more non-duplicate entries into
~/.Xauthority
as well. Ideally we would clean our entries up when the connection closes, but that's more of a nice-to-have and not part of this PR.Note that X11 forwarding is still only supported by OpenSSH clients (
coder config-ssh
), this PR did not add X11 forwarding support tocoder ssh
.Fixes#14198