Bug 234007 - umask not honored by file resource
Summary: umask not honored by file resource
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kab3
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-11 05:54 UTC by Marcel Cary
Modified: 2016-09-24 19:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel Cary 2010-04-11 05:54:22 UTC
Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Unlisted Binary Package

I would like a simple way to share an addressbook with other local users.  In the past, I've done it with a file resource.  With this version, it seems to no longer work.

To replicate the bug:

Set everyone's umask to 002 by opening konsole, running "umask 002", and starting kontact from that konsole (to factor out any issues with whether umask is set correctly for the X session).  As user1, create a new file resource, for example, ~user1/tmp/abc.vcf.  It will be created according to umask (so far so good).  As user2, who shares default group with user1's default group, and who also can write to ~user1/tmp/, create a file resource using the same file name.  Now, as user2, add an address.  The file will be recreated with permissions 0600, aka -rw------- (surprising, and breaks my address sharing solution).  user1 will see message, "Unable to open file: '/home/user1/tmp/abc.vcf'".

Desired behavior:

I expect user2's addressbook to recreate the file according to user2's umask, which would preserve the group read/write access.  Actually, this worked as I expected in a prior version of KDE.

Work around:

After editing the file, manually chmod g+rw $file.  The permission change will stick for several edits, as long the *other* user does not edit the resource.

This seems to affect korganizer in the same way.

I see support for an akonadi resource, but that seems to slow everything down and it's not clear to me that it supports multi-user sharing (perhaps it only shares between a single user's many applications and devices).
Comment 1 Denis Kurz 2016-09-24 19:53:53 UTC
Thank you for your efforts you put into this bug. kab3 has long been deprecated, and so I close its old reports. If this bug/wish is still valid for kab3's successor kaddressbook in any recent version (5.0 or later, as part of KDE Applications 15.08.0 or later), please file a new bug against kaddressbook.