[Maverick] smb4k_sudowriter changes file permissions on /etc/sudoers

[Tom Hobson]

Binary package hint: smb4k

When enabling superuser options in SMB4k (so unprivileged users can mount shares) smb4k_sudowriter modifies the file permissions on /etc/sudoers from 440 to 640 breaking sudo system wide.

I am running Xubuntu 10.10 Alpha 3

lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10

apt-cache policy smb4k
smb4k:
  Installed: 0.10.7-1
  Candidate: 0.10.7-1
  Version table:
 *** 0.10.7-1 0
        500 http://au.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages
        100 /var/lib/dpkg/status

Additional:
booting into recovery and using "chmod 440 /etc/sudoers" usually fixes the damage but sometimes breaks gdm. Attempting to mount shares once said fix has been implemented results in smb4k throwing the following error: "mount error: could not resolve address for $HOSTNAME: no address associated with hostname" where $HOSTNAME is the computer you are trying to connect to. This occurs with both the workgroup view, search and manual entry. Should I fork this as a separate bug?

[Charlie Kravetz (cjkgeek)]

I am adding this as a "security" bug report, since it appears smb4k is changing permissions of /etc/sudoers.

[Jamie Strandboge (jdstrand)]

This definitely needs to be fixed, but having mode 640 when the owner is root is not a security vulnerability since root can write to a 440 file just as easily as a 640 file. I'm assuming it is not changing the ownership. Please verify it is still owned by root:root and if not, remark this as security.

[Tom Hobson (es02)]

/etc/sudoers stays root:root for me.

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Debian/Bugs. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Tom Hobson (es02)]

Upstream bug link: https://developer.berlios.de/bugs/?func=detailbug&bug_id=17481&group_id=769

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

Thank you for sending the issue upstream.

Thanks for taking the time to make Ubuntu better!