db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6258) Restrict permissions on BACKUP.HISTORY
Date Tue, 25 Jun 2013 11:38:20 GMT

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

ASF subversion and git services commented on DERBY-6258:

Commit 1496425 from [~knutanders]
[ https://svn.apache.org/r1496425 ]

DERBY-6258: Restrict permissions on BACKUP.HISTORY

Merged revision 1492110 from trunk.
> Restrict permissions on BACKUP.HISTORY
> --------------------------------------
>                 Key: DERBY-6258
>                 URL: https://issues.apache.org/jira/browse/DERBY-6258
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions:,
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>             Fix For:
>         Attachments: derby-6258-01-a.diff
> DirFile4.getOutputStream(boolean) does not restrict the file permissions on the file
if it ends up creating a new file.
> This method is only used for writing to BACKUP.HISTORY during backup. The BACKUP.HISTORY
file in the backup does have restricted file permissions, it is only the file in the original
database that is created with less restrictive permissions.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message