Live data from Hacker News

Real Terminal, All Chrome

blog.koding.com

61–70 of 112 posts

Re: Real Terminal, All Chrome

#62
post #49
post #48

Earlier quoted context omitted.

>> Oh, I mean I wasn't impressed with the terminal emulator itself. At least when I tried it, it seemed to have problems with some ctrl-sequences (as in, other things would get them instead of whatever I was running in the terminal emulator). This is true, my go-to text mode editor (yes you can laugh) nano has Ctrl-O for write-out and that brings up the ChromeOS open dialog instead. It's most irritating. I might wait…

Heat is absolutely a problem with the current Pixel. My suspicion is that the Pixel can probably cool itself well under loads you would expect in ChromeOS, but if you fall outside of that usage pattern it becomes problematic. (There probably aren't a lot of ways to peg the CPU at 100% for minutes on end in ChromeOS while not in dev-mode.) > if there is one. Yeah, that is a big if. I don't have any sort of sales figur…

> There probably aren't a lot of ways to peg the CPU at 100% for minutes on end in ChromeOS while not in dev-mode.

Load a webpage with just one or two screenshot-sized animated GIFs. Browsers are really bad at this; I wonder how many years it's been since the GIF rendering code was touched in most implementations.

Re: Real Terminal, All Chrome

#63
post #60
post #43

Earlier quoted context omitted.

The intermediate, untrusted computer (in this case koding.com's VM) can read my password.

This isn't really the intended use case, sshing from your Koding VM to other servers. However the VM we give you is yours - you have root and full control over it, if there is something on there to capture your passwords then you put it there :) (We are not the NSA)

That is the least convincing security statement I've heard in a long time. So what if we have root access? You can still log everything or compromise the vm under the hood -- and there really is no way to prove otherwise AFAICT (trusting trust and whatnot). In this case, the NSA would least of my concerns!

Re: Real Terminal, All Chrome

#64
post #32
post #31

so let me get this straight... they wrote a terminal app that sends all your code to some third party? wow yeah lets just throw security out the window. no mention of the privacy implications on any of this. not sure if any of my clients would want their intellectual property sent out to some random third party. thanks but no thanks. i'd rather use xterm or gnome-terminal.

or github, aws etc. Oh yeah thats right, couldnt use those either. I guess you host everything yourself on a private network that you install all the connectivity for globally ?

I don't think this should be downvoted, since of course it is also technically possible for Amazon to snoop on your EC2 servers. However, Koding's generic privacy policy and 404ed terms of service are not that inspiring on the matter.

Re: Real Terminal, All Chrome

#65
post #26
post #23

Earlier quoted context omitted.

I think he meant (and I initially assumed from the headline) effectively bash in the browser, running locally.

you're right, but local bash in the browser is technically not possible for now. (if you don't hack or bridge the chrome). It can be an emulator or a connector like the secure-shell app by Google in Chrome store. Terminal app provides a free and full terminal with Koding VM.

It's certainly possible to run a GNU userland on top of NaCl, though it would be highly nontrivial.

Re: Real Terminal, All Chrome

#66

Earlier quoted context omitted.

They are providing an easy way to create a sandbox to code or learn to code. A simple use case would be if you were to teach a class on coding that required a Linux environment to compile C, but the students brought their own laptops, you could A. Struggle with all the possible laptop configurations and how to install VMs and/or the proper packages on those computers or B Use koding.com and have everyone do their pro…

Indeed, this fits my use case to an absolute tee right now. I'm trying to pick up Rails, and doing anything related under a Windows environment is downright painful, and I'd rather not dualboot just to get into "work mode". A free VM I can access with any browser? Awesome.

Why not spin up an Ubuntu VM in VMware or virtualbox? I'm not knocking the koding terminal, but "I want a Unix environment without dual-booting" is a fairly standard VMware use case.

Re: Real Terminal, All Chrome

#67
post #60
post #43

Earlier quoted context omitted.

The intermediate, untrusted computer (in this case koding.com's VM) can read my password.

This isn't really the intended use case, sshing from your Koding VM to other servers. However the VM we give you is yours - you have root and full control over it, if there is something on there to capture your passwords then you put it there :) (We are not the NSA)

[deleted]

Re: Real Terminal, All Chrome

#68
post #63
post #60

Earlier quoted context omitted.

This isn't really the intended use case, sshing from your Koding VM to other servers. However the VM we give you is yours - you have root and full control over it, if there is something on there to capture your passwords then you put it there :) (We are not the NSA)

That is the least convincing security statement I've heard in a long time. So what if we have root access? You can still log everything or compromise the vm under the hood -- and there really is no way to prove otherwise AFAICT (trusting trust and whatnot). In this case, the NSA would least of my concerns!

I don't disagree with what your saying, however all security when there is a third party involved who can see what your doing in the clear is based on trust. We do everything we can to make sure that the only people who could possibly see what your doing is us. Should you trust us ? thats up to you. But ask yourself why we would risk everything we have built just to steal your passwords/keys ? If we did that we would be the most expensive and elaborate social engineering attack I have ever heard of :) anyway - come to the platform, do some not so serious stuff then over time maybe we can gain your trust ?

Re: Real Terminal, All Chrome

#69
post #64
post #32

Earlier quoted context omitted.

or github, aws etc. Oh yeah thats right, couldnt use those either. I guess you host everything yourself on a private network that you install all the connectivity for globally ?

I don't think this should be downvoted, since of course it is also technically possible for Amazon to snoop on your EC2 servers. However, Koding's generic privacy policy and 404ed terms of service are not that inspiring on the matter.

whoops that 404 is a regression. Just fixed - thanks for the heads up.

Re: Real Terminal, All Chrome

#70
post #26
post #23

Earlier quoted context omitted.

I think he meant (and I initially assumed from the headline) effectively bash in the browser, running locally.

you're right, but local bash in the browser is technically not possible for now. (if you don't hack or bridge the chrome). It can be an emulator or a connector like the secure-shell app by Google in Chrome store. Terminal app provides a free and full terminal with Koding VM.

> local bash in the browser is technically not possible for now.

Yes it is, and I've seen it. It was posted to HN a while (like about a year or two) ago, and could run emacs etc. It was done by emulating x86 in Javascript and then running Linux on the emulator.

Post reply on HN