Open wiredfool opened 1 year ago
I ran into the same problem today. @wiredfool have you found a workaround to get it running via Tailscale?
Running into this when trying to setup console1984, rails console audits, and want to pass through the real tailscale user accessing the system - since a rogue person could login as any system user, not necessarily one that corresponds to the TS one.
It looks like this was fixed in v1.76.0
What are you trying to do?
I'm trying to set environment variables on the remote server.
In
~/.ssh/config
(or for testing, usingssh -o SendEnv=GIT_COMMITTER_NAME server
)and a corresponding sshd_config of:
Logging into the server using the host ssh daemon sets environment variables in the login shell as expected:
Doing the same via the tailscale ssh doesn't set the environment variables.
How should we solve this?
Either document the way to set AcceptEnv for the tailscale ssh daemon, or set some way of doing it.
What is the impact of not solving this?
It's currently a speed bump in a rollout where there are destinations that need to have different git preferences, depending on which identity is logging into the server, using the
users: [autogroup:noroot]
acl.The existing system currently works (system sshd), but has all of the drawbacks of not using tailscale ssh.
Anything else?
No response