[ 
https://issues.apache.org/jira/browse/DERBY-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266445#comment-13266445
 ] 

Dag H. Wanvik commented on DERBY-5442:
--------------------------------------

Thanks for patch 2, Kim! Only one comment, but cf Knut's suggestions above 
also. I think in ref man section derby.storage.useDefaultFilePermissions, we 
should remove the texual explanation in the bullets:

(quote)
"- f you set the property to true, the Network Server uses whatever default 
file permissions the user has set for their system.
  -  If you set the property to false, access is limited not only for files 
created by the Network Server when it is started from the command line, but 
also for embedded databases and for databases managed by servers which are 
started programmatically inside application code using the Derby API. This 
enhances security for all database files.
"

since this is better explained below in the matrix. [Btw: The bullets points 
speak of  "the network server", which is misleading here, since by setting the 
property, Derby will use specified behavior also in embedded mode (as shown in 
the matrix)].
                
> 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
>
>         Attachments: DERBY-5442-2.diff, DERBY-5442-2.zip, DERBY-5442.diff, 
> DERBY-5442.stat, DERBY-5442.zip
>
>


--
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

        

Reply via email to