mobile-shell / mobile-shell/mosh
feature request - reverse shell
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 14.5k
- Forks
- 865
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I manage a shit ton of Linux/Android devices behind a NAT'd 3G network, I just found Mosh now and I was like OMG this is such an awesome tool exactly what I was hoping. For a 3G network the latency and packet loss are the norm. So I happily chose Mosh. But there's a problem with NAT, you need first somehow VPN or tunnel into the intranet and then mosh to individual devices, it would be cool if mosh devices could connect to a centralized server with a public IP, then I can just connect to the central server to connect to each devices.
Is it possible with some kind of hack, and is this feature within the scope of Mosh?
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 files or tests are named. Start by examining Mosh's existing client/server connection flow and how NAT affects device reachability; determine whether centralized public-server and reverse-connection support are in scope, then define a concrete protocol and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp, linux
- Domain
- cli, distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100