Timeline for Bad edit to sudoers file on EC2 instance, how to fix it?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 28, 2017 at 6:26 | answer | added | lakshayk | timeline score: 1 | |
| Jul 27, 2017 at 13:01 | vote | accept | Adonis | ||
| S Jul 26, 2017 at 20:28 | history | suggested | T K Sourabh | CC BY-SA 3.0 |
Updated description
|
| Jul 26, 2017 at 20:17 | review | Suggested edits | |||
| S Jul 26, 2017 at 20:28 | |||||
| Jul 26, 2017 at 20:11 | answer | added | T K Sourabh | timeline score: 1 | |
| Jul 26, 2017 at 18:18 | answer | added | TheAce | timeline score: 5 | |
| Jul 26, 2017 at 16:12 | answer | added | James Shewey | timeline score: 1 | |
| Jul 26, 2017 at 15:47 | answer | added | Xiong Chiamiov | timeline score: 4 | |
| Jul 26, 2017 at 15:08 | comment | added | Adonis |
@KlwntSingh True, but without access to the sudo command, the ec2-user cannot perform any root command, which is the core of the issue (perhaps it was confusing!)
|
|
| Jul 26, 2017 at 15:05 | comment | added | KlwntSingh | you can download some sample sudoers file and make sudoers work. | |
| Jul 26, 2017 at 13:34 | review | First posts | |||
| Jul 26, 2017 at 15:14 | |||||
| Jul 26, 2017 at 13:30 | history | asked | Adonis | CC BY-SA 3.0 |