sudo 1.7.2

I have created PETs for sudo in the Quirky repo, usable by all Woof-built puppies:

yes|sudo||exe,dev,doc,nls

The PETs (51KB, 32KB, 47KB):
http://distro.ibiblio.org/quirky/pet_packages-quirky/sudo-1.7.2.pet
http://distro.ibiblio.org/quirky/pet_packages-quirky/sudo_DEV-1.7.2.pet
http://distro.ibiblio.org/quirky/pet_packages-quirky/sudo_DOC-1.7.2.pet

The main PET only has 'sudo', and does not have /etc/sudoers. There is a template for sudo in Woof that deletes /etc/sudoers in any other sudo package. /etc/sudoers is intended to be supplied in rootfs-skeleton.

The DEV PET has 'visudo', used to edit /etc/sudoers.


Posted on 3 May 2011, 15:39


Comments:

Posted on 3 May 2011, 24:12 by tronkel
/etc/sudoers
/etc/sudoers can only be edited using visudo

Any user with sudo privileges has to be included in this file e.g. for user "another_user"

# User privilege specification
root ALL=(ALL:ALL) ALL
another_user ALL=(ALL:ALL) ALL

Works this way in Ubuntu.Worth a try


Posted on 4 May 2011, 3:01 by L18L
Re /etc/sudoers
"/etc/sudoers can only be edited using visudo "
No. root can do it, spot can do it, you can do it:
# mp /etc/sudoers
And I did it, copied Barry's entries into it. See my comment "Having Fun With Sudo"

Using "another_user ALL=(ALL:ALL) ALL" would mean giving spot root privileges in general.

The problem which has not yet been solved is just getting the password...


Posted on 4 May 2011, 7:52 by scottman
may be of use...
http://www.clearchain.com/blog/posts/freebsd-sudo-upgrade-gone-wrong-password-no-longer-working-with-sudo-1-7-2p2-1-7-2p3-sudo-broken

this link may be helpful... apparently some later sudo versions break pam, and dodgy visudo setup can cause constant bad passwords as well..