Timeline for Recommending sudoedit instead of sudo $editor?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 30 at 9:46 | comment | added | NeoH4x0r | Sudoedit creates a copy of the file, and you work on the copy in a unprivileged context, after you save it sudoedit will copy the file back with the appropriate privileges. So yeah, no need to worry about commands running as root. | |
| Dec 30, 2015 at 11:16 | comment | added | dcorking | As far as I can tell from the sudoedit manual, the editor doesn't run with superuser privileges, so that shell escapes aren't the danger you suggest. | |
| Nov 27, 2011 at 16:46 | history | edited | keepitsimpleengineer | CC BY-SA 3.0 |
Additional remarks hopefully increasing undersanding
|
| Nov 27, 2011 at 16:44 | comment | added | keepitsimpleengineer | Jorge - I've expanding my thinking in an edit | |
| Nov 27, 2011 at 16:40 | history | edited | keepitsimpleengineer | CC BY-SA 3.0 |
Additional remarks hopefully increasing undersanding
|
| Nov 27, 2011 at 1:59 | comment | added | Jorge Castro | I don't get why it wouldn't be a recommendation. For normal people they would get nano, and everyone else would get whatever editor they defined. | |
| Nov 27, 2011 at 0:08 | history | answered | keepitsimpleengineer | CC BY-SA 3.0 |