[
https://issues.apache.org/jira/browse/QPID-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324034#comment-14324034
]
Keith Wall commented on QPID-6247:
----------------------------------
Slight broadening the scope of the jira, I think any configuration object that:
# creates a new file that contains config (config.json, passwd, group) should
respect a context var providing a posix permission string e.g. ""rwxr-x---"
# updates an existing file that contains config should maintain the existing
permissions of the file throughout the update process. This needs to be done
in such a way that any temporary file does not become momentatily visible.
Out of scope:
# On windows, we wouldn't apply the default permission string, but we would
strive to maintain permissions on update.
# Non configuration files created by Qpid (e.g. derby, je files, log files)
> 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: Improvement
> 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: [email protected]
For additional commands, e-mail: [email protected]
