Timeline for Security against malicious script edits
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 22, 2016 at 11:54 | comment | added | Thomas Ward Mod | You also didn't read my first section where I say: "but it's up to the users to determine whether they are comfortable running commands posted in answers." That's the other part of it. | |
| Apr 22, 2016 at 11:53 | comment | added | Thomas Ward Mod | @SimonT So you didn't read my first section about the community moderation. Most "malicious" edits like that are already caught by the reviewers - I don't see anyone usually with unmoderated edit privileges walking around making those types of edits. Not without the mods bringing down a hammer on them fast, or the community doing the same. | |
| Apr 22, 2016 at 2:48 | comment | added | SimonT |
To play devil's advocate, suppose some malicious user were to edit the /dev/null section into /dev/sda (or something that works, which I'm not going to test on my machine). Many users would have just copy and pasted the line without too much thought.
|
|
| Apr 21, 2016 at 22:00 | history | answered | Thomas WardMod | CC BY-SA 3.0 |