harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4754) [classlib] FilePermission incorrect canonical path
Date Thu, 06 Sep 2007 18:34:32 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525492

Mark Hindess commented on HARMONY-4754:

I also notice that the RI doesn't evaluate the canonical path in the constructor but only
when it is required ... for example when the implies method is called.  This might result
in different behaviour if the filesystem changes between the call to new and the call to implies.
 We should probably try to behave more like the RI.

> [classlib] FilePermission incorrect canonical path
> --------------------------------------------------
>                 Key: HARMONY-4754
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4754
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>            Reporter: Mark Hindess
> If called with a path ending in "-" or "*", java.io.FilePermission calls  File.getCanonicalPath
with the "-" or "*" still appended.  This is incorrect (and produces very odd results if "-"
or "*" exists - perhaps as a symlink to some completely different tree).
> For example, if you do:
>   mkdir test
>   ln -s /tmp test/-
>  then (new FilePermission("test/-", "read")).implies(new FilePermission("/tmp/file",
> is true and (new FilePermission("test/-", "read")).implies(new FilePermission("test/file",
"read") is false where as on the RI it is the opposite way around since the '-' symlink is
(correctly) ignored.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message