Bug 102367 - FILEOPEN: wrong file permission of lock file under unix
Summary: FILEOPEN: wrong file permission of lock file under unix
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-22 18:06 UTC by Sven
Modified: 2017-05-31 10:47 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven 2016-09-22 18:06:54 UTC
Hi all, 

in our company we use the default umask 077, so that all new saved documents become the file permission
-rw------- example.odt

After the document was saved the user changes the file permission, so that other users can edit the file too; e.g. 
-rw-rw-rw- example.odt

The lock file but still get the permission based on the default umask
-rw------- .~example.odt#

When a second user now open the document, he doesn't get a warning dialog that another user is editing the document. The document will open normally and the second user can edit the document too.
The second user has no permission to read the lock file. When the second user becomes the permission to read the log file the warning dialog is shown.

Is it possible, that the lock file will always be written ignoring the umask that the file will become read permissions for owner, group and other?

Thanks a lot
Comment 1 Buovjaga 2016-10-09 14:06:33 UTC
I think you should try asking here first: http://ask.libreoffice.org/

Set to NEEDINFO.
Change back to UNCONFIRMED, if AskLibO did not help. Change to RESOLVED WORKSFORME, if you got a solution from AskLibO.
Comment 2 QA Administrators 2017-05-02 11:37:36 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2017-05-31 10:47:15 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20170531