[
http://issues.apache.org/jira/browse/DERBY-622?page=comments#action_12372386 ]
Andrew McIntyre commented on DERBY-622:
---------------------------------------
Followup:
I can confirm that both with and without the change in the _step1 patch, and
with or without the policy file change to remove the lines marked Bug:
DERBY-622, that adding the following line to the permissions of derby.jar and
derbynet.jar in derby_tests.policy for each of the locale jars fixes the
difference that is seen in the tests:
permission java.io.FilePermission
"${derbyTesting.codejar}derbyLocale_${LOCALE}.jar", read
where ${LOCALE} is one of the supported locale jar files removes the
corresponding line from the diff in the test.
> sysinfo incorrectly requires permission on Derby jar files
> ----------------------------------------------------------
>
> Key: DERBY-622
> URL: http://issues.apache.org/jira/browse/DERBY-622
> Project: Derby
> Type: Bug
> Components: Security, Tools
> Versions: 10.2.0.0
> Reporter: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: DERBY-622_step1.diff
>
> Running the test derbynet/sysinfo.java requires this permission in
> derby_tests.policy, in order to read the jar files.
> permission java.io.FilePermission "${csinfo.codedir}${/}*", "read"
> But according to the Java security specs:
> 'Note: code can always read a file from the same directory it's in (or a
> subdirectory of that directory); it does not need explicit permission to do
> so.'
> Probably means a privileged block is required when accessing the contents of
> the jar files in sysinfo
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
