DigiKam and ACL

[Toby Dickenson]

Bjarne Wichmann Petersen wrote:

> On Monday 02 October 2006 23:37, Toby Dickenson wrote:
> 
>> I recommend adding "session optional pam_umask.so umask=002"
>> to /etc/pam.d/common-session. This sets the umask to 002 for all logins.
> 
> Am I correct in understanding that I need to install libpam_umask for this
> to work?

Correct.
 
> DigiKam *insists* on not allowing anyone but the owner write-access for
> any files it creates.

Which files in particular?

> You must have done something else to make DigiKam behave. ;-)

Interesting.

Ive just checked the behaviour of digikam 0.8.2~rc1-0ubuntu3 using strace.
Downloaded photos are definitely being created with a mode 0666 (so
permissions get set entirely by umask). This is with a USB mass storage
camera; I guess other camera types _might_ be different.

It looks like the digikam3.db database would be created with 0644
permissions. So yes, I must have changed this manually at some point. It
currently has 0664, and I am **sure** I havent changed those permissions
recently.

Interestingly, while modifying the database sqlite does create its journal
file (digikam3.db-journal) with permissions 0644. This would not be
writable by other users in the group. This file is used for recovery if
digikam crashes in the middle of an update. I wonder what would happen if
that recovery needed to be performed by different user to the one who had
the crash?