[
https://issues.apache.org/jira/browse/DERBY-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078545#comment-13078545
]
Dag H. Wanvik commented on DERBY-5363:
--------------------------------------
With JDK 7, more is available to control permissions for POSIX-like file
systems and ACLs as in NTFS, cf. the tutorial here:
http://download.oracle.com/javase/tutorial/essential/io/fileAttr.html
This page:
http://download.oracle.com/javase/tutorial/essential/io/legacy.html
shows that the java.io.File#{setWritable,setReadable} made available in Java 6
are now superceded in Java 7 by the new metadata
stuff. Cf the package java.nio.file.attribute and java.nio.file.*.
We may want to consider the opportunities opened by this instead of going with
the limited facilities in Java 6.
> Tighten default permissions of DB files with >= JDK6
> ----------------------------------------------------
>
> Key: DERBY-5363
> URL: https://issues.apache.org/jira/browse/DERBY-5363
> Project: Derby
> Issue Type: Improvement
> Reporter: Dag H. Wanvik
>
> Before Java 6, files created by Derby would have the default
> permissions of the operating system context. Under Unix, this would
> depend on the effective umask of the process that started the Java VM.
> In Java 6 and 7, there are methods available that allows tightening up this
> (File.setReadable, setWritable), making it less likely that somebody
> would accidentally run Derby with a too lenient default.
> I suggest we take advantage of this, and let Derby by default (in Java
> 6 and higher) limit the visibility to the OS user that starts the VM,
> e.g. on Unix this would be equivalent to running with umask 0077. More
> secure by default is good, I think.
> We could have a flag, e.g. "derby.storage.useDefaultFilePermissions"
> that when set to true, would give the old behavior.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
