db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5363) Tighten default permissions of DB files with >= JDK6
Date Fri, 30 Sep 2011 18:03:45 GMT

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

Mike Matrigali commented on DERBY-5363:
---------------------------------------

It is already strange that one will get different behavior depending on which JVM one uses.
 There is a precedent when we added JVM locking support to prevent dual booting the behavior
was different depending on JVM version, so documentation/explanation is key to let users
know what to expect.

It seems more straight forward to only support the change with jdk17 and up JVM's.  It is
easily documented, and I assume implemented.  Users upgrading to a new JVM should be looking
for consequences to their applications and hopefully at that point will 
run tests.  

It also seems like testing of the feature is more straight forward with this restriction.
 
                
> 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-followup.diff,
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

        

Mime
View raw message