Skip to content
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

per socket ssh options #2583

Closed
totaam opened this issue Feb 10, 2020 · 4 comments
Closed

per socket ssh options #2583

totaam opened this issue Feb 10, 2020 · 4 comments
Labels

Comments

@totaam
Copy link
Collaborator

totaam commented Feb 10, 2020

Issue migrated from trac ticket # 2583

component: network | priority: major | resolution: fixed

2020-02-10 04:14:39: antoine created the issue


#2460 was for ssl, this is for ssh.

@totaam
Copy link
Collaborator Author

totaam commented Feb 10, 2020

2020-02-10 04:24:56: antoine changed status from new to closed

@totaam
Copy link
Collaborator Author

totaam commented Feb 10, 2020

2020-02-10 04:24:56: antoine set resolution to fixed

@totaam
Copy link
Collaborator Author

totaam commented Feb 10, 2020

2020-02-10 04:24:56: antoine commented


Done in r25200.

The ssh server sockets now honour two new options:

  • ssh-gss-host
  • ssh-host-key

ie:

xpra start --start=xterm --bind-tcp=0.0.0.0:10000,ssh-host-key=./ssh_host_ed25519_key -d ssh

Will use the host key specified rather than the default ones.
Especially useful since the host keys in /etc/ssh/ssh_host_*.key are usually not accessible for non-root users.

@totaam totaam closed this as completed Feb 10, 2020
@totaam
Copy link
Collaborator Author

totaam commented Oct 12, 2020

2020-10-12 13:06:04: antoine commented


See also r27656. SSH socket upgrades can now be configured on a per-socket basis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant