[
https://issues.apache.org/jira/browse/DERBY-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116372#comment-13116372
]
Knut Anders Hatlen commented on DERBY-5363:
-------------------------------------------
One small issue that I didn't notice until now. sysinfo outputs this on Java 7
after the commit:
--------- Derby Information --------
JRE - JDBC: ?-?
I think JVMInfo.derbyVMLevel() needs to be updated now that Java 7 isn't
handled as Java 6 anymore.
> 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
> Components: Miscellaneous, Services, Store
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Attachments: derby-5363-basic-1.diff, derby-5363-basic-1.stat,
> derby-5363-basic-2.diff, derby-5363-basic-2.stat, derby-5363-basic-3.diff,
> derby-5363-basic-3.stat, derby-5363-full-1.diff, derby-5363-full-1.stat,
> derby-5363-full-2.diff, derby-5363-full-2.stat, derby-5363-full-3.diff,
> derby-5363-full-3.stat, derby-5363-full-4.diff, derby-5363-full-4.stat,
> derby-5363-full-5.diff, derby-5363-full-5.stat, derby-5363-server-1.diff,
> permission-5.diff, permission-5.stat, permission-6.diff, permission-6.stat,
> property-table.png, releaseNote.html, releaseNote.html, releaseNote.html,
> releaseNote.html, z.sql
>
>
> 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.
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
