db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-5492) Restrictive file permissions: permissions removed also for owner on NTFS if Acl does not contain explicit entry for owner
Date Wed, 09 Nov 2011 09:41:51 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dag H. Wanvik closed DERBY-5492.
--------------------------------

          Resolution: Fixed
       Fix Version/s: 10.9.0.0
            Assignee: Dag H. Wanvik
    Issue & fix info:   (was: Patch Available)
    
> Restrictive file permissions: permissions removed also for owner on NTFS if Acl does
not contain explicit entry for owner
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5492
>                 URL: https://issues.apache.org/jira/browse/DERBY-5492
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.9.0.0
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>             Fix For: 10.9.0.0
>
>         Attachments: derby-5492-1.diff, derby-5492-1.stat, derby-5492-2.diff, derby-5492-2.stat
>
>
> It turns out that the file owner does not necessarily get an explicit AclEntry; this
depends on whether the created file has sufficient permissions already through, say, a permission
for everybody to write. The present logic removes all AclEntries except those granted to the
file's owner, erroneously presuming there would be such an entry always. This led to all AclEntries
being removed. 
> This error is seen in Oracle's nightly regressions for Windows, but did not reproduced
when running manually on Windows. This was due to different default inherited permissions
on the directories in which the regression tests were run.

--
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