3 ms·
As viraptor said, putting code into a public repository (e.g., debian packages); that way there should be a paper trail if the code is modified. Beyond that, t
by cperciva 10y ago
As viraptor said, putting code into a public repository (e.g., debian packages); that way there should be a paper trail if the code is modified.
Beyond that, there's a simple matter of advertising: "Share your terminal (read-only)" may mislead some people about what is happening. A more accurate description would be "Give us control of your terminal (we promise we'll only let other people read it, not write anything)".
- emodendroket 10y agoImagine if this principle were applied to other software products. "Click here to download the Office installer, which will gain full admin-level access to your machine. We promise to only use that to install Office."
- cperciva 10y agoThat would be awesome. Users might start to understand security.
- emodendroket 10y agoUsers don't read.
- vitorbaptistaa 10y agoAs usual, you can never be sure unless you read the code, luckily, it's very small: https://github.com/vitorbaptista/shellshare/blob/master/public/bin/shellshare https://github.com/vitorbaptista/shellshare/blob/master/publ... The only thing sent to shellshare's servers is the text in your bash terminal. There's no return channel for the servers to send commands back to the computer. You could argue that you're giving control of the terminal because you're running a third-party executable, but that's the same for any executable you run.