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

Xterm.js

xtermjs.org

Post reply on HN
Print view View original

11–20 of 67 posts

Re: Xterm.js

#11

Post by rbanffy »

emilfihlman wrote: post #6
hulitu wrote: post #3

"Build terminals in the browser" ... and give your passwords there, and type commands. What can go wrong.

Running in the browser is no more (or less) untrusted than running a dedicated terminal client.

When was the last case when a malicious website or script could capture content or keystrokes directed at another tab? Really curious, because it seems an obvious attack vector.

Re: Xterm.js

#13

Post by noergl »

emilfihlman wrote: post #6
hulitu wrote: post #3

"Build terminals in the browser" ... and give your passwords there, and type commands. What can go wrong.

Running in the browser is no more (or less) untrusted than running a dedicated terminal client.

I tend to disagree. The fact, that a browser engine and JS is involved raises the bar significantly during security audits. It brings additional third-party players into the chain you have to trust. Meanwhile I suggest to read https://xtermjs.org/docs/guides/security/.

Re: Xterm.js

#15

Post by colejohnson66 »

rbanffy wrote: post #11
emilfihlman wrote: post #6

Earlier quoted context omitted.

Running in the browser is no more (or less) untrusted than running a dedicated terminal client.

When was the last case when a malicious website or script could capture content or keystrokes directed at another tab? Really curious, because it seems an obvious attack vector.

At least in the last decade, I don’t think that’s even possible on the “big” browsers. There were vulnerabilities involving s, but I don’t know enough about those.

Re: Xterm.js

#16

Post by fimdomeio »

just throwing a related idea in here in the hopes someone finds it interesting enough to develop.

Having a very simple cli app generator that allows one to have independent terminal applications that run just like normal app. Independent in the sense that you can open them as any other app, run on their own window, and and you can reach them through the app switcher.

Re: Xterm.js

#17

Post by rasengan »

Fun fact - xterm.js was originally created by chjj who also wrote the code for Handshake DNS among other things.

My favorite is blessed [1].

He’s definitely a super programmer. Thank you for all your contributions to this world @chjj!

[1] https://github.com/chjj/blessed

Re: Xterm.js

#18

Post by williamstein »

rasengan wrote: post #17

Fun fact - xterm.js was originally created by chjj who also wrote the code for Handshake DNS among other things. My favorite is blessed [1]. He’s definitely a super programmer. Thank you for all your contributions to this world @chjj! [1] https://github.com/chjj/blessed

term.js was originally created by Fabrice Bellard -- see the headers of @chjj's term.js file [1]. Bellard wrote term.js since he needed a way to interact with his amazing port [2] of Linux to a web browser. Term.js had a non-open-source license and @chjj spent time a decade ago successfully convincing Bellard to relicense term.js open source (I watched and greatly appreciated this as it happened!). Xterm.js is a very significant rewrite and improvement of term.js, mostly done by Daniel Imms who is on the VS Code team at Microsoft; xterm.js is a great contribution of Microsoft to open source, and is used at VS Code's terminal. I watched all this happen over the years, visited Daniel at Microsoft, etc.; I think this is all very useful tech (e.g., we use it in JupyterLab and CoCalc).

[1] https://github.com/chjj/term.js/blob/master/src/term.js

[2] https://bellard.org/jslinux/

Re: Xterm.js

#19

Post by mbreese »

fimdomeio wrote: post #16

just throwing a related idea in here in the hopes someone finds it interesting enough to develop. Having a very simple cli app generator that allows one to have independent terminal applications that run just like normal app. Independent in the sense that you can open them as any other app, run on their own window, and and you can reach them through the app switcher.

If you're on a Mac, you can do this with AppleScript.

If you open the Script Editor, you can use this chunk of code to get started:

    tell application "Terminal"
     do script "~/test.sh"
    end tell
This will run the script ~/test.sh in a new terminal window. Closing the window automatically is a bit more difficult, but it can also be done. You can save this as an Application, which will let you click to open it, just like any other application.

See here for more information:

https://stackoverflow.com/questions/1870270/sending-commands...

https://stackoverflow.com/questions/27453987/how-to-close-a-...

Post reply on HN