You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, the problem here is that we are being sloppy and allowing SSH's controlling terminal to be the user's /dev/tty (not the pty). That way SSH gets input from the keyboard (e.g. the password) without our having to ferry the keystrokes to SSH. Unfortunately it also means when SSH writes directly to the tty (as it does for the password prompt, but not "Permission denied"), we never get it and it just goes straight to the terminal.
Fixing this would take some more sophistication: we would need a poll loop to ferry keystrokes to SSH and then SSH's output to the terminal, except we'd probably want to screen out the "MOSH IP" line, which is trickier when we are going byte-by-byte.
I'm inclined to leave this as-is for now, at least for 1.0.
This was filed nearly 10 years ago, and we've had lots of changes to the mosh startup script since. It's unclear to me this issue still exists. Please reopen if you can reproduce with mosh 1.4.0
Some error messages from the initial ssh connection appear after the password prompt is reprinted. For example, when inputting an incorrect password:
aroach@champignon:~$ mosh champignon
aroach@champignon's password:
aroach@champignon's password: Permission denied, please try again.
The text was updated successfully, but these errors were encountered: