Red Hat Bugzilla – Bug 558875
no valid sudoers sources found
Last modified: 2010-04-23 15:45:41 EDT
Description of problem:
#sudo sudo: parse error in /etc/sudoers near line 96
sudo: no valid sudoers sources found, quitting
Version-Release number of selected component (if applicable):
I had to remove all comments after "root ALL=(ALL) ALL" to make it work.
This appears to be because of the newly added #includedir directive. It looks like sudo barfs if the included dir is empty which I failed to test when suggesting adding this feature, sorry about that.
IMO this sounds like a upstream bug; I don't think an empty included dir should be a problem. Apart from getting a real fix for that, one way to work around it would be to add let's say a /etc/sudoers.d/README containing valid sudoers format comments, something like the attached patch (README is intentionally a non-%config file even though rpmlint complains about it).
Created attachment 394420 [details]
Add placeholder README to /etc/sudoers.d
From the ChangeLog:
Major changes between version 1.7.2p1 and 1.7.2p2:
* No longer produce a parse error when #includedir references a directory that contains no valid filenames.
Seems to be a regression. I'm going to investigate this and hopefully do a new build tomorrow.
Ok, it's not a regression... the fix didn't made it to the release tarball (don't know why). Here are the cvs commits:
the toke.l part is present in the 1.7.2p2 tarball but the toke.c part is not. So I guest it's a mistake. Reported upstream and a new build for rawhide is on the way.
New build: http://koji.fedoraproject.org/koji/taskinfo?taskID=1992154
Discussed at today's blocker review meeting. Two of us confirmed that current F13 sudo, sudo-1.7.2p6-1.fc13.x86_64 , seems to behave fine. We're closing this; please re-open if we're missing something. Thanks!
Fedora Bugzappers volunteer triage team