| Summary: | ASTERISK-08453: /etc/sudoers file becomes corrupt | ||
| Reporter: | Jay Phillips (jicksta) | Labels: | |
| Date Opened: | 2006-12-28 15:56:41.000-0600 | Date Closed: | 2007-01-02 09:28:04.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I labeled this bug as "unable to reproduce" because I'm not sure *when* this happened, but debugging it should be relatively easy. The bug prevents use of "sudo" to gain superuser access and can only be fixed by using exclamation mark commands in the Asterisk CLI on the physical machine (to my knowledge). It seems a script tried to echo the string "admin ALL=(ALL) ALL" to the end of /etc/sudoers, but didn't put a newline before it. I noticed this when I shelled in as admin and then tried to run a command with sudo. I got an error as follows: [admin@localhost ~]$ sudo -s >>> sudoers file: syntax error, line 29 <<< sudo: parse error in /etc/sudoers near line 29 [admin@localhost ~]$ On line 30 (29 was a commented line), I had the following (obviously malformed) line: admin ALL=(ALL) ALLadmin ALL=(ALL) ALL So it seems there was an issue with something trying to set the privileges for the admin account by echoing this into the /etc/sudoers file, even though the file contained the exact string it was trying to add. Fixing it I imagine would be as simple as a "find /path/to/trunk | xargs grep /etc/sudoers" and seeing where it may try to append-echo something to it. | ||
| Comments: | By: Brandon Kruse (bkruse) 2006-12-31 23:17:04.000-0600 this was fixed in beta2 ( from what i understand ) update | ||