Open Joerger opened 2 years ago
I'm getting this on macOS 13.1, using tsh version 11.2.3. Using tsh ssh works fine, but using ssh does not
I see this also on Rocky Linux 8 with teleport 10.1.4. Command:
tsh login --proxy=my.proxy.net --user=myuser
works from a terminal but errors when called from a bash script.
tsh login --proxy=my.proxy.net --user=myuser
Welcome to SERVER. All activity will be logged.
Press [ENTER] to continue.
ERROR: underlying reader is not a terminal
This effect is seen where tsh is expecting to read input from a yubikey.
If the remote proxy triggers a URL-based auth, the process works fine.
tsh login --proxy=other.proxy.int --user=otheruser
If browser window does not open automatically, open it by clicking on the link:
http://127.0.0.1:39159/3a026c04-6b6d-441e-b03b-a9facfeb4e6d
+1
MobaXterm Version 23.2 (2023-06-25) resolves this issue.
Expected behavior:
Successfully
tsh login
in MobaXterm terminal.Current behavior:
Request fails with
underlying reader is not a terminal
error.Workaround:
Instead, you have to login with Command Prompt or another terminal. Then you can use MobaXterm for other
tsh
commands.This method requires that your Command Prompt and MobaXterm terminals both have access to
~/.tsh
, either by sharing a home directory or setting$TELEPORT_HOME
.Bug details:
tsh login
from MobaXterm terminal