Live data from Hacker News

Secure Shell chrome (killer) app

chrome.google.com

161–170 of 178 posts

Re: Secure Shell chrome (killer) app

#161

Earlier quoted context omitted.

Can you post the syntax of how you included the identity file. The parsing keeps grabbing my user@host in with the -i id.pem Connecting to -i id.pem user@host, port 22... Loading NaCl plugin... done. Warning: Identity file id.pem user@host not accessible: No such file or directory.

I first ssh'd into me@localhost. From that point, ssh automatically discovers key files in ~/.ssh. This explains why my Keychain did not work, since I was logged into a "remote" host.

Ah, that makes sense and is a nice workaround. Thanks for the reply!

Re: Secure Shell chrome (killer) app

#162

Earlier quoted context omitted.

I think Nacl is portable. But it wouldn't run on Android right now anyway since the Chrome browser on Android doesn't have access to the Chrome webstore and extensions.

NaCL is not portable, unless you happen to be running the same architecture that the software was compiled for. You might be thinking of PNaCL which is still very experimental: http://www.chromium.org/nativeclient/pnacl

[deleted]

Re: Secure Shell chrome (killer) app

#163

Earlier quoted context omitted.

I think Nacl is portable. But it wouldn't run on Android right now anyway since the Chrome browser on Android doesn't have access to the Chrome webstore and extensions.

NaCL is not portable, unless you happen to be running the same architecture that the software was compiled for. You might be thinking of PNaCL which is still very experimental: http://www.chromium.org/nativeclient/pnacl

Well that's just dumb. They should've made ARM a first citizen for ChromeOS from day one. I saw a rumor about a future Samsung Chromebook that will use a dual core 2 Ghz Cortex A15 chip, so maybe it's coming soon.

Re: Secure Shell chrome (killer) app

#164
post #39
post #36

Earlier quoted context omitted.

No. from the page "It uses Native-Client to connect directly to ssh servers without the need for external proxies." it IS a ssh client. no http proxies.

That's right. But Secure Shell also knows how to connect to an HTTP-to-ssh relay.

Most clients yes. That one, not sure.

Re: Secure Shell chrome (killer) app

#165
post #23

Can someone please explain to me why I would possibly want to run a terminal emulator inside of my web browser, instead of just using the terminal emulator app that my system ships with?

So I used to think the same thing, and then I saw something funny: it was a spinning 3D cube with a scrolling document on all 6 faces. It was made with pdf.js and WebGL. Now this isn't the same because it's NaCl and therefore not pure-web, but a pure-web terminal emulator would be awesome! It would mean you could embed it within normal web content and mash it up with other stuff. Want to edit your dropbox contents/Gm…

I can understand that having an open-source library that provides the ability to embed a terminal emulator might be useful somewhere, to someone. But as a full-screen plugin for Chrome?

Re: Secure Shell chrome (killer) app

#166
post #23

Can someone please explain to me why I would possibly want to run a terminal emulator inside of my web browser, instead of just using the terminal emulator app that my system ships with?

So I used to think the same thing, and then I saw something funny: it was a spinning 3D cube with a scrolling document on all 6 faces. It was made with pdf.js and WebGL. Now this isn't the same because it's NaCl and therefore not pure-web, but a pure-web terminal emulator would be awesome! It would mean you could embed it within normal web content and mash it up with other stuff. Want to edit your dropbox contents/Gm…

The only part about this written in NaCl is the "ssh" command. The terminal emulator portion of it is entirely JS.

The only reason it isn't currently cross-browser is because I don't have enough time in the day to make it work everywhere. I tried not to make it too Webkit specific though. If some brave JS hacker/Firefox user wants to make this cross browser, I'd be happy to help.

Re: Secure Shell chrome (killer) app

#167
post #86
post #23

Can someone please explain to me why I would possibly want to run a terminal emulator inside of my web browser, instead of just using the terminal emulator app that my system ships with?

As a followup, my terminal windows are rarely the same size as my browser windows. I don't like resizing my browser windows in general because the browser will remember the new size, even though it was meant as a once-off window. So having a browser-sized terminal doesn't seem like a very good experience. Additionally, it doesn't even work right. In a screen-controlling app like vim it seems fine, but in the normal s…

The missing lines at the bottom is a bug that got fixed just after this release. The next Secure Shell release won't have the issue.

And your browser size issue goes away if you open the terminal in its own window. Chrome even has an "Open as Window" option (right click on the Secure Shell icon) to open in a window with no browser UI.

Re: Secure Shell chrome (killer) app

#168
post #166

Earlier quoted context omitted.

So I used to think the same thing, and then I saw something funny: it was a spinning 3D cube with a scrolling document on all 6 faces. It was made with pdf.js and WebGL. Now this isn't the same because it's NaCl and therefore not pure-web, but a pure-web terminal emulator would be awesome! It would mean you could embed it within normal web content and mash it up with other stuff. Want to edit your dropbox contents/Gm…

The only part about this written in NaCl is the "ssh" command. The terminal emulator portion of it is entirely JS. The only reason it isn't currently cross-browser is because I don't have enough time in the day to make it work everywhere. I tried not to make it too Webkit specific though. If some brave JS hacker/Firefox user wants to make this cross browser, I'd be happy to help.

Ah, pretty awesome then. (I can't change my previous reply though, due to time limits)

Re: Secure Shell chrome (killer) app

#169
post #23

Can someone please explain to me why I would possibly want to run a terminal emulator inside of my web browser, instead of just using the terminal emulator app that my system ships with?

Windows! I spend most of my time coding in PuTTy + Vim when I'm on windows. In my limited testing this works as I expect with xterm-256, tmux, and Vim on my Ubuntu 12.04 Server without having to configure anything. PuTTy is a pain to configure on a new box.

tmux didn't work as expected for me. i.e. I could attach to my tmux sessions, as well as switch between the "panes" - but I couldn't see the status bar.

I also started a new tmux instance (rather than attach to existing one) still no status bar. Any suggestions ?

Edit : Problem solved. I went into Full screen mode (F11) after clicking in addressbar (When focus was on the terminal, F11 printed ~) Anyway, when I started tmux in full screen mode, I could see tmux status bar. I continued to see it even after I left full screen.

Not sure what was the (temporary) problem.

Re: Secure Shell chrome (killer) app

#170
post #23

Can someone please explain to me why I would possibly want to run a terminal emulator inside of my web browser, instead of just using the terminal emulator app that my system ships with?

the complete list of software i use day-to-day consists of a web browser and a terminal emulator. if i switched over to this, that list goes down to just a browser. maybe some people don't care, but i think it's pretty cool.

It's the difference between Ctrl-Tab and Cmd-Tab, no?
Post reply on HN