Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jabref changes the file permissions of the database #2279

Closed
g-mos opened this issue Nov 16, 2016 · 3 comments · Fixed by #2281
Closed

Jabref changes the file permissions of the database #2279

g-mos opened this issue Nov 16, 2016 · 3 comments · Fixed by #2281

Comments

@g-mos
Copy link

g-mos commented Nov 16, 2016

JabRef version 3.7 on Ubuntu 16.04

If you save the database it changes the permissions of the file to 600 (read/write for user and no access to anybody else). This can be a problem in shared databases where all users belong to the same group, but are different users.

@lenhard
Copy link
Member

lenhard commented Nov 17, 2016

JabRef uses standard Java classes to write the file on save, essentially an OutputStreamWriter. I guess the permissions of the file are somehow derived from the permissions of the user that executes the process. For the record: What are the permissions before they are re-written by JabRef? What happens when other programs implemented in Java write to that shared folder your database is in? Do permissions change?

I am not yet convinced that your problem is not due to the configuration of your system. Lacking a Ubuntu installation, I cannot verify your problem unfortunately.

@lenhard lenhard added the status: waiting-for-feedback The submitter or other users need to provide more information about the issue label Nov 17, 2016
@g-mos
Copy link
Author

g-mos commented Nov 17, 2016

Jabref version 3.6 did not have that problem. Let's say that you have a file with rw permissions for user/group/everyone. In v3.6 when you save it the permissions stay the same. In v3.7 they change to rw for user and no access for group/everyone.
Therefore I believe it has to do with changes in the latest version.

@lenhard lenhard removed the status: waiting-for-feedback The submitter or other users need to provide more information about the issue label Nov 17, 2016
@lenhard
Copy link
Member

lenhard commented Nov 17, 2016

Thanks for the reply @g-mos! If 3.6 is doing this correctly in your environment, then so should 3.7.

I am a little bit at a loss as to what might be causing this behavior, but maybe one of the other developers knows more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants