db-derby-dev mailing list archives

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

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

Dag H. Wanvik updated DERBY-5492:
---------------------------------

    Attachment: derby-5492-1.stat
                derby-5492-1.diff

Uploading a patch which makes two changes:

- Construct a new AclEntry for the owner with all rights, and removed existing ones (NTFS).
This should handle the error seen in Oracle's regressions.

- For Solaris/ZFS and similar file systems which support both Posix file attributes view and
ACLs, don't touch the ACLs but stick to the Posix flags.

Rerunning regressions of NTFS, Solaris/ZFS and Linux.

                
> 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
>         Attachments: derby-5492-1.diff, derby-5492-1.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 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