[
https://issues.apache.org/jira/browse/DERBY-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239960#comment-13239960
]
Kim Haase commented on DERBY-5442:
----------------------------------
It looks as if the default when you don't set the new property
derby.storage.useDefaultFilePermissions is different from the behavior when you
set it to either false or true. Am I understanding this correctly? I'm looking
at the last version of the release note for DERBY-5363.
If you don't set it (and you run using Java 7), the Derby Network Server limits
access for Derby-created files and directories to the user account that booted
the server.
If you set it to true, the server uses whatever default file permissions the
user has set for their system.
If you set it to false, access is limited not only for files created by the
Network Server, but also for embedded databases and for databases managed by
servers which were started programmatically inside application code via the
Derby API.
So once you have set the property one way or the other, the way to return to
the default behavior is to restart the server without setting the property.
I'm looking into where this should be documented, other than the property
documentation in the Reference Manual:
Developer's Guide: the section "Configuring security in a client/server
environment", which talks about operating system permissions for files. There
should at least be a mention of the feature.
Admin Guide: Maybe a new topic under "Derby Network Server advanced topics"?
The feature is related to Network Server security. This new topic might be
cross-referenced from "Starting the Network Server".
If you have any other locations in mind, please let me know. I may find some
more myself.
> Create documentation for restrictive file permissions feature
> -------------------------------------------------------------
>
> Key: DERBY-5442
> URL: https://issues.apache.org/jira/browse/DERBY-5442
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Dag H. Wanvik
> Assignee: Kim Haase
> Fix For: 10.9.0.0
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
