Maybe the begining of an understanding : jghali irced this quote from http://en.wikipedia.org/wiki/Umask#Processes
"Each process has its own mask, which is applied whenever the process creates a new file. When a shell, or any other process, spawns a new process, the child process inherits the mask from its parent process.[7] When the process is a shell, the mask is changed by the umask command. As with other processes, any process launched from the shell inherits that shell's mask." And added : "there may be a difference of behavior depending if scribus is installed locally or system wide" JL Le 10/12/2013 21:35, Mark Heieis a ?crit : > Hi > > I just repeated a simple test. > > 1) set my umask to 0002 > 2) created a 1 page doc > 3) added single, existing jpg image from ~/sub-directory that had 664 > 4) saved document to home (~) directory. > > resultant sla got 664, as expected. > > 5) collected4 output to home (~) and shared subdirectories, both had 775 plus > g+s for shared one. The result in both > cases the collected document had 664 (as expected), the "images" directory > created by Scribus had 775 (as expected) but > the image file had 600 (not as expected)! At least for the home dir, all file > permissions should be set to according to > umask. > > *** So something is not respecting the umask conditions. So I don't see this > as a conflict in choosing which file > permission settings to use for security purposes, especially when saving > within user home context. > > I'm wondering whether it is something that happens (overriding?) or not > happening (being set?) within QFileInfo as I > can't see any explicit setting of the umask/permissions in the src (could > have missed it though). > > BTW - tested with 1.5.0svn > > mrh. > > > On 2013-12-10 11:37, Craig Bradney wrote: >> On 10/12/2013 8:27 pm, Joe Zeff wrote: >>> On 12/10/2013 02:18 AM, Craig Bradney wrote: >>>> I agree that Scribus should maintain ownership settings on files however >>>> the idea that it should >>>> change permissions on files based on the parent directory permissions is >>>> false. There's no >>>> standard saying that a directory's settings must determine the file >>>> settings at all, anywhere on >>>> any OS . >>> AIUI, the default perms for a file are those of the directory it's in, or >>> those of the umask of >>> whoever creates it, whichever is more restrictive. >>> >> That may be the case however if a directory is 755, and files within a 600, >> then what should Scribus >> follow? There would be a reason someone has set them to 600 rather than 755 >> (whether that be >> manually, umask or otherwise), and for Scribus to assume that when it >> collects for output into a >> directory that has 755 set, with a collected file with 600 set, that it >> should convert that to >> 755... would be incredibly wrong. >> >> Craig >> >> >> ___ >> Scribus Mailing List: scribus at lists.scribus.net >> Edit your options or unsubscribe: >> http://lists.scribus.net/mailman/listinfo/scribus >> See also: >> http://wiki.scribus.net >> http://forums.scribus.net > > > ___ > Scribus Mailing List: scribus at lists.scribus.net > Edit your options or unsubscribe: > http://lists.scribus.net/mailman/listinfo/scribus > See also: > http://wiki.scribus.net > http://forums.scribus.net >
