News for hackers. Stuff that matters.
Re:Mosh v1.3 Released by apostacy on Saturday April 29, 2017 @06:23PM (#14229103)
I'm sure there are good security reasons. ssh is very conservative about how it is invoked.
Re:Mosh v1.3 Released by geofft on Saturday April 29, 2017 @07:14PM (#14229308)
Mosh already negotiates an ssh connection, so I think you can do this safely - attempt to execute mosh-server, if the execution fails, open a normal shell and proxy the data back to the original screen.

You probably don't want mosh to do the proxying, since ssh (the client) is a pretty involved program - it handles signals, it supports port-forwarding, etc.

I sort of suspect SSH ControlMaster would work. I could imagine a mosh client script that sets ControlMaster=yes and a random ControlPath, tries to mosh, and runs ssh -o ControlMaster=no if it fails. And then unconditionally does an ssh -o ControlMaster=no -O exit.

Re:Mosh v1.3 Released by xmichael99 on Saturday April 29, 2017 @06:30PM (#14229128)
No, it is only a terminal.

mosh [email protected] [email protected]'s password: bash: mosh-server: command not found Connection to 192.168.1.10 closed. /usr/local/bin/mosh: Did not find mosh server startup message. (Have you installed mosh on your server?)

I'm pretty sure they could just change it to execute /usr/local/bin/mosh;/bin/bash without much of an issue. As that is all it is, it is a terminal.