mobile-shell / mobile-shell/mosh
Connection impossible if the `mosh-server` command does not terminate (Nix + proot)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 14.5k
- Forks
- 865
- PR merge metrics
- No merged PRs in 30d
Description
If mosh-server does not terminate and the SSH session stays open, mosh won't progress. As a result the server will time out, after which the client gets started and times out as well.
For some reason JuiceSSH is not affected by this (it probably starts the client as soon as it sees the CONNECT line).
I was facing this situation because I was running mosh-server under proot, which only terminates when all of its child processes terminate. After identifying this issue I could work around it with a wrapper:
exec 3< <(YOUR_MOSH_SERVER_CMD "$@")
grep -m 1 CONNECT <&3
This looks like a wontfix to me, but it should be useful info for other people having similarly exotic environments 😄.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named in the issue. It documents a mosh-server/SSH timing problem under proot, offers a shell-wrapper workaround, and does not define a requested change or completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, shell
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100