Timeline for Dangers of piping to stdin of process in another terminal
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2021 at 19:47 | comment | added | db-inf | Don't worry. Also is not a synonym of always. | |
| Nov 29, 2021 at 9:43 | comment | added | Chris Davies | Db-inf generally it's better not to run day to day as root. Very little will stop you doing so, because it's your mschine, but it's better to do stuff as a normal user for as much of the time as possible | |
| Nov 29, 2021 at 9:30 | comment | added | db-inf | On your Part 2. What you are saying, is that when I mess up, it's my own authorized mess. Thanks for the reassurance. The problem is that I am also the root of my private personal computer, and a linux newbie. | |
| Nov 29, 2021 at 9:25 | comment | added | db-inf | On your Part 1, I actually did read that question before daring mine. I looked up the TIOCSTI you commented on there, and it hightened my fear, because Simulate terminal input is exactly what seems dangerous to me. Gilles 'SO- stop being evil' too had in his anser the possibility If /proc/PID/fd/0 is a pipe, then writing to it appends the data to the pipe's buffer. In that case, the process that's reading from the pipe will read the data. And then in the accepted answer the stdX are linked to /dev/pty#, mine to /dev/pts/#. | |
| Nov 27, 2021 at 13:20 | history | answered | Chris Davies | CC BY-SA 4.0 |