You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2014/11/24 20:12:13 UTC
[jira] [Created] (QPID-6247) Updates to Json configuration stores
should maintain existing file permissions
Keith Wall created QPID-6247:
--------------------------------
Summary: Updates to Json configuration stores should maintain existing file permissions
Key: QPID-6247
URL: https://issues.apache.org/jira/browse/QPID-6247
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Keith Wall
Priority: Minor
If I cause a change to made to the broker configuration (say, adding a port) or the configuration of a virtualhost backed by a json file (say adding a queue), the Broker rewrites the underlying file(JsonFileConfigStore). However, in doing so, the file's original file permissions may be lost. In a POSIX based system, get the default permissions specified by the umask.
The user can workaround the issue by setting as suitably restrictive umask, but this will currently apply to all files created by Broker, even log files which a user may wish to carry a different permission, for operate reasons.
The Java Broker should strive to maintain permissions on such file by attempting to replacement file with the same permission set/attribute view as the old.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org