https://bugzilla.novell.com/show_bug.cgi?id=293429#c9 Bernhard Kaindl <bk@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bk@novell.com |security-team@suse.de Status|ASSIGNED |NEW --- Comment #9 from Bernhard Kaindl <bk@novell.com> 2007-08-20 15:14:47 MST --- You have to decide. It seems that suid is also needed when using hal as I found in "man gnome-mount", gnome-mount seems to call /sbin/mount directly, when it finds a matching entry in /etc/fstab: In addition to using HAL as the mechanism for mounting file sys‐ tems, the /etc/fstab file is also consulted as HAL will refuse to mount any file system listed in this file as it would violate system policy. If this is the case, gnome-mount will invoke mount(1) as the calling user rather than invoking the Mount method on the org.freedesktop.Hal.Device.Volume interface on the device object representing the volume / drive. This means that settings (mount point, mount options, file system type) read by gnome-mount are not passed along as these are already specified in the /etc/fstab file and there are no mechanism to override them. When parsing the /etc/fstab file, gnome-mount (and also HAL for that matter) resolves symbolic links and also respects the LABEL= and UUID= notations. For example, if this line is in /etc/fstab LABEL=MyVolume /mnt/myvolume auto user,defaults 0 0 then gnome-mount mounts the file system with the label MyVolume via mount(1) and /etc/fstab rather than using the HAL mecha‐ nisms. I checked the hal source and and found that "HAL will refuse to mount any file system listed in this file as it would violate system policy" is true, so for a non-root user to be able to mount ntfs partitions which were entered into /etc/fstab, ntfs-3g needs to be suid root in any case. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.