On Fri, Feb 25, 2005 at 06:37:39PM +0100, Martin Pitt wrote: > Hi Michael! > > Michael Schmitt [2005-02-25 18:07 +0100]: > > Package: pmount > > Version: 0.7.1-1 > > Severity: wishlist > > > > /dev/sdc2 on /media/foobar type vfat > > (rw,noexec,nosuid,nodev,quiet,uid=1033,gid=46,umask=077) > > That is how a drive gets mounted as I plug it in (USB), but I need some > > facility to tweak that behavior. I use gnome-volume-manager and I am not > > absolutely sure that this bugreport is sent to the right place, maybe gvm > > and > > hal needs to be tweaked too to get what I wish. Any hints would be > > appreciated. > > Right now pmount does not offer an option to modify the umask. This is > in order to avoid exposing the new device (which may contain GPG keys > and other secret stuff) to the world. > > I'm not opposed to the idea of an umask option.
Right nothing wrong with giving the user the option to expose his/her secrets to the world right ;).. Although the current behaviour should obviously stay the default. > However, something has > to supply the new option; normally the device policy is read out from > hal (by pmount-hal) and passed to pmount. > > So where and how do you think this policy should be configured? I guess in/by hal like the other mount options. volume.policy.mount_option.gid sound good to me ? Only downside is that it's then a system wide policy and not a user one. This could be a nice use-case for use-specific fdi files.. Although debian and ubuntu are the only distro's where it would be usefull Sjoerd -- In order to live free and happily, you must sacrifice boredom. It is not always an easy sacrifice.
signature.asc
Description: Digital signature
