Group permissions problem

[Al Gordon]

On 2/20/06, Al Gordon <runlevel7 at gmail.com> wrote:
> I tried this (setting umask in a script in /etc/X11/Xsession.d/) and
> it didn't work for me.  My shell user did, in fact, get the new umask,
> but anything created through the gui still had the same permissions as
> before.
>
> I noticed a similar conversation here, with no conclusive results:
> http://lists.debian.org/debian-gtk-gnome/2004/09/msg00005.html
>
> Debian bug #254840 is referenced in this, but from what I can tell,
> that bug is closed with the directions edit the files in
> /etc/X11/Xsession.d/ instead of /etc/login.defs.
>
> It really seems like umask is hard coded somewhere, like in X or
> nautilus or something.  When/if I get time, I might look at source
> code to see if I can find references to it there.  Wish me luck, as
> I'm no programmer.  ;)
>
> --
>
>   -- AL --

Follow up: Searching Malone led me to this:
http://bugzilla.gnome.org/show_bug.cgi?id=327249

quoted:

Bug 327249 – nautilus ignores umask
View Bug Activity  |  Clone This Bug
Product: 	gnome-vfs
Component: 	File operations
Version: 	2.13.x
Status: 	NEW
Priority: 	Normal
Severity: 	normal
Opened by nahoo82 terra es (points: 4)
2006-01-16 19:49 UTC [reply]

Fordwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314796

Hi,

while trying to set a global umask for my users via gdm, I discovered
that nautilus simply refuses to use any umask. Even when the session's
umask is set to something non default and other gnome programs obey it
(gedit, evolution,...), nautilus keeps on creating files with 600 as
permissions.

This makes it impossible to use nautilus in a network environment with
shared folders.

Thanks for your tremendeous work,

///////

I've tested this on nautilus 2.12, creating a .gnomerc with the needed umask,
but nautilus always uses 600 as umask.


Comment #1 from Christian Neumair (gnome-vfs developer, points: 21)
2006-01-16 20:13 UTC [reply]

Thanks for your bug report!

I'm reassigning this to GnomeVFS. We're hard-coding 0666 in
gnome-vfs-xfer.c:xfer_create_target which is passed to gnome_vfs_create_uri,
pass  0600 to fchmod in gnome-vfs-private-utils.c:gnome_vfs_create_temp, and
pass 0777 to gnome_vfs_make_directory_for_uri in
gnome-vfs-xfer.c:create_directory.

I think what permissions are used should be decided inside GnomeVFS. Maybe we
should pass umask permissions, and the modules should decide whether they care
or not.



--

  -- AL --