Live data from Hacker News

A native graphical shell for SSH

probablymarcus.com

131–140 of 239 posts

Re: A native graphical shell for SSH

#131
post #73

This appears to me like a solution in search of a problem, like many others before it...the quote below seems relevant to this effort. "Those who do not understand Unix are condemned to reinvent it, poorly." ~Henry Spencer

I hired a programmer and after giving him his Linux laptop let him set up a few things. A couple hours later he asked me where he could get PuTTY for it, and I recognized a huge gap in my interview coverage.

Ever hired someone who, when you ask them to send you an ssh key for access to something, sends you their private key? Yeah, that's happened more than once.

Re: A native graphical shell for SSH

#132

This appears to me like a solution in search of a problem, like many others before it...the quote below seems relevant to this effort. "Those who do not understand Unix are condemned to reinvent it, poorly." ~Henry Spencer

No. It’s just that now more people are using Linux the more the ux decisions that were made 40 years ago will be questioned. Almost all dev facing machines have ssh server installed and accessible. Why ssh terminal has to look like character-only trash from 1960s? Why a TUI is the best thing we pipe through ssh? Why I cannot watch a 4k movie in the terminal or browse the web using pinch to zoom ?

> Why ssh terminal has to look like character-only trash from 1960s?

We should re-implement it with Comic Sans and happy shiny buttons to click everywhere? Click here for "ls -alh" ?

Re: A native graphical shell for SSH

#133

i'm trying to understand how outer shell works here. on the website you give the following as your motivation: > Apps like Jupyter and Tensorboard are not typically visible to standard web browsers if they’re running on remote servers, because it would be terribly unsafe to let the whole internet touch this app. Instead, they run on a local port on the server, which your computer can’t access directly. > Classically,…

HTTP basic auth is not secure.

Re: A native graphical shell for SSH

#135

Earlier quoted context omitted.

At the risk of being considered a snob I don’t want someone who can’t deal with SSH or RDP configuring servers within my company. If you can’t work out how to SSH into the server you sure as hell aren’t going to work out how to safely expose network services on it.

Within your company, sure. But there's some engineers (think medical) who know standards like DICOM and PACS imaging but aren't familiar at all with OS internals or systems administration.

If you’re not a sysadmin, there’s no reason to wrestle around with OS internals and system tools. We have moved away from mainframes and now everyone is root on one’s computer, but honestly anything in /etc, /sbin and /usr/sbin should be irrelevant for daily workflows.

Re: A native graphical shell for SSH

#136
post #73

Earlier quoted context omitted.

I hired a programmer and after giving him his Linux laptop let him set up a few things. A couple hours later he asked me where he could get PuTTY for it, and I recognized a huge gap in my interview coverage.

Gotta auto-reject anyone listing Windows experience on resume

wow, what a way to prejudice against people fluent in multiple paradigms

Re: A native graphical shell for SSH

#137

This appears to me like a solution in search of a problem, like many others before it...the quote below seems relevant to this effort. "Those who do not understand Unix are condemned to reinvent it, poorly." ~Henry Spencer

No. It’s just that now more people are using Linux the more the ux decisions that were made 40 years ago will be questioned. Almost all dev facing machines have ssh server installed and accessible. Why ssh terminal has to look like character-only trash from 1960s? Why a TUI is the best thing we pipe through ssh? Why I cannot watch a 4k movie in the terminal or browse the web using pinch to zoom ?

because it is TEXT

you want your GUI then set up VNC

Re: A native graphical shell for SSH

#138
post #62

Do not do this. There are many, many excellent long-standing security and "web control plane isolation" reasons browsers are not permitted generic socket permissions. The closest mechanical analog that comes to mind is why 3-wheeled ATVs are a bad idea.

I think it's okay as long as: - sockets are blocked by default, until they are added to an allow-list explicitly on the server side - True sudo awareness ensures root sockets aren't reachable without the sudo password. (This capability is important, because otherwise you create an incentive for people to run root backends with user-accessible sockets.) More here: https://outerloop.sh/security/

There’s no such thing as a root socket. Stop using that phrase.
Post reply on HN