Open flybyray opened 2 years ago
Just happened upon this issue. This basically happens because when TLS routing is enabled, we need the TLS certificate in addition to the forwarded agent key to connect to the proxy.
This should be solved once https://github.com/gravitational/teleport/issues/1648 is complete, which we expect to land in a minor release of v12.
Description
tsh config
ssh -A jumphost
access to specialapp
(based on native-ssh) run in intranet behind(fw
)tsh config
could be used with the identities forwarded fromlaptop
dbhost
this UX is not working with tls-routing enabled
jumphost
thetsh config
now usestsh proxy ssh
which tries to read identies from files onjumphost
question: is it technically possible to use the identities forwarded from
laptop
withtsh proxy ssh
fromjumphost
?What would you like Teleport to do?
Finish the
tsh proxy ssh
implementation to support the ssh ProxyCommand UX.What problem does this solve?
tsh proxy ssh
should provide same UX as native-ssh ProxyCommand reading ssh-agents identities and keys.If a workaround exists, please include it.
one of the following helped:
laptop
could betsh scp
'ed to thejumphost
v2
config explicit add the listen addresses to proxy service. the old native-ssh with forwarded agent ssh-config would work againIn case this is more a bug then a feature the errors are
References