db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (DERBY-5363) Tighten default permissions of DB files with >= JDK6
Date Mon, 26 Sep 2011 16:55:27 GMT

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

Dag H. Wanvik edited comment on DERBY-5363 at 9/26/11 4:55 PM:
---------------------------------------------------------------

I had a new regression error. It turned out that after I changed to implicit fixure addition,
the indeterministic test fixture ordering resulting under Java 7 intermittently exposed a
bug: If the test containing the jar file install were executed prior to the backup test, the
database would contain a jar file which is, of course, then also backed up. There was code
to to handle this, but it wasn't part of the test (except by this "accident") and it had a
bug. Fixed now in version *-full-5, which I upload. Rerunning regressions.

      was (Author: dagw):
    I had a new regression error. It turned out that after I changed to implicit fixure addition,
the indeterministic test fixture ordering resulting under Java 7 intermittently exposed a
bug: If the test containing the jar file install were executed prior to the backup test, the
database would contain a jar file which is, of course, then also backed up. There was code
to to handle this, but it wasn't part of the test and it had a bug. Fixed now in version *-full-5,
which I upload. Rerunning regressions.
  
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message