Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mosh: The Mobile Shell

mosh.org

Post reply on HN
Print view View original

91–100 of 158 posts

Re: Mosh: The Mobile Shell

#91

Post by input_sh »

foxpurple wrote: post #32
dang wrote: post #2

Some past threads: Blink Mobile Shell for iOS (Mosh Based) - https://news.ycombinator.com/item?id=18370348 - Nov 2018 (1 comment) Mosh: the mobile shell - https://news.ycombinator.com/item?id=12429203 - Sept 2016 (49 comments) Mosh: the mobile shell - https://news.ycombinator.com/item?id=11572146 - April 2016 (148 comments) Mosh – a robust, responsive replacement for SSH - https://news.ycombinator.com/item?id=8928506…

The title “Mosh: SSH for 2012” is amusing because now in 2021, ssh is still king.

I disagree. SSH is fine for short connections (like git push or running some Ansible playbook), but it's far too fragile for longer uses. For example, if you're running something like dd with no output, you end up in a situation where you're not sure if dd is still running or did your connection just break.

With mosh, I could start dd, close my laptop, move to a cafe, open up my laptop, and know for certain I'll re-establish the connection when I'm back online.

Re: Mosh: The Mobile Shell

#92

Post by gsich »

input_sh wrote: post #91
foxpurple wrote: post #32

Earlier quoted context omitted.

The title “Mosh: SSH for 2012” is amusing because now in 2021, ssh is still king.

I disagree. SSH is fine for short connections (like git push or running some Ansible playbook), but it's far too fragile for longer uses. For example, if you're running something like dd with no output, you end up in a situation where you're not sure if dd is still running or did your connection just break. With mosh, I could start dd, close my laptop, move to a cafe, open up my laptop, and know for certain I'll re-e…

If you have long running operations you can use screen/tmux.

Re: Mosh: The Mobile Shell

#93

Post by kseistrup »

banana_giraffe wrote: post #24
rattray wrote: post #23

Earlier quoted context omitted.

Link? Any tradeoffs?

They're talking about Eternal Terminal, I think https://eternalterminal.dev/ I'd be curious about the trade offs too, I'll have to check it out.

The way I see it, mosh has an advantage over et: while mosh is started on connection as the remote and unprivileged user, et relies on etserver running as root on the remote box (after connection is established, etterminal runs as the unprivileged user, though), so any vulnerabilities in etserver may have serious consequences.

Re: Mosh: The Mobile Shell

#95

Post by radicality »

keithwinstein wrote: post #43
shp0ngle wrote: post #4

Note that Mosh has not had release for 4 years, even when pull requests are accepted on github, and the team lead says "we are too busy/burned out". https://github.com/mobile-shell/mosh/issues/1115

I think the truth is that we don't feel like we need a release. We've never had a security hole, our track record speaks for itself, and I wouldn't really want us to rush anything and blow that. There are some features that it would be really nice to have in a release (like 24-bit color support, and working around a recent MacOS clock bug), but I handed over the maintainership to somebody else about six years ago and…

Thanks for the tool! I use it all the time, even just now I’m on a crappy connection via cellular modem that oscillates from few bars LTE, to 3G at I like the philosophy here, if the software is “done” and there is no immediate need for security fixes, don’t touch it.

Re: Mosh: The Mobile Shell

#96

Post by LAC-Tech »

I use this for my VPS which is a 4 hour plane journey from me. It's a lifesaver.

Mosh really is an un-sung hero when it comes to software. Especially for those of us in the middle of nowhere :)

Re: Mosh: The Mobile Shell

#97

Post by blueflow »

shp0ngle wrote: post #4

Note that Mosh has not had release for 4 years, even when pull requests are accepted on github, and the team lead says "we are too busy/burned out". https://github.com/mobile-shell/mosh/issues/1115

IT is one of the few places in the industry where its seen as a problem or a fault if a project is finished and fulfills its purpose.

Re: Mosh: The Mobile Shell

#98

Post by j1elo »

keithwinstein wrote: post #43
shp0ngle wrote: post #4

Note that Mosh has not had release for 4 years, even when pull requests are accepted on github, and the team lead says "we are too busy/burned out". https://github.com/mobile-shell/mosh/issues/1115

I think the truth is that we don't feel like we need a release. We've never had a security hole, our track record speaks for itself, and I wouldn't really want us to rush anything and blow that. There are some features that it would be really nice to have in a release (like 24-bit color support, and working around a recent MacOS clock bug), but I handed over the maintainership to somebody else about six years ago and…

omg I can visualize all those pull requests or feature requests on the TCP repo: "It would be a nice addition if TCP also did ..."

Re: Mosh: The Mobile Shell

#99

Post by Shish2k »

gsich wrote: post #92
input_sh wrote: post #91

Earlier quoted context omitted.

I disagree. SSH is fine for short connections (like git push or running some Ansible playbook), but it's far too fragile for longer uses. For example, if you're running something like dd with no output, you end up in a situation where you're not sure if dd is still running or did your connection just break. With mosh, I could start dd, close my laptop, move to a cafe, open up my laptop, and know for certain I'll re-e…

If you have long running operations you can use screen/tmux.

You can use screen/tmux, but they’re both more complicated and less good when it comes to this specific use-case.

Personally I use both - mosh (or et) for the seamless automatic-reconnect, and tmux as a console window-manager.

Re: Mosh: The Mobile Shell

#100

Post by dspillett »

keithwinstein wrote: post #43
shp0ngle wrote: post #4

Note that Mosh has not had release for 4 years, even when pull requests are accepted on github, and the team lead says "we are too busy/burned out". https://github.com/mobile-shell/mosh/issues/1115

I think the truth is that we don't feel like we need a release. We've never had a security hole, our track record speaks for itself, and I wouldn't really want us to rush anything and blow that. There are some features that it would be really nice to have in a release (like 24-bit color support, and working around a recent MacOS clock bug), but I handed over the maintainership to somebody else about six years ago and…

> I think the truth is that we don't feel like we need a release.

Maybe issue a point release where the only change is updating the documentation (man page, output of --version, ...) to state that it is 2021 and you are still here, stable, free of security issues, but not adding/updating features ATM. Then the project doesn't look dead (which can be a security concern) when it is in fact just quietly carrying on with achieving its goals without the need for changes.

Post reply on HN