[
https://issues.apache.org/jira/browse/DERBY-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-3086:
---------------------------------
Attachment: derby-3086-02-removeDerbyTesting-aa.diff
Thanks for catching this, Dan. Attaching
derby-3082-02-removeDerbyTesting-aa.diff. This patch removes the derbyTesting
grants from the server policy file. It turns out that the sysinfo class in
derbyTesting lives in a different package than the production sysinfo in the
other jar files. So it would not be the class resolved by the production
invocations of sysinfo.
> The server policy needs to grant derbynet.jar more permissions so that
> sysinfo and drda tracing will work
> ---------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3086
> URL: https://issues.apache.org/jira/browse/DERBY-3086
> Project: Derby
> Issue Type: Bug
> Components: Security
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-3086-01-morePermissions-aa.diff,
> derby-3086-01-morePermissions-ab.diff, derby-3086-01-morePermissions-ac.diff,
> derby-3086-02-removeDerbyTesting-aa.diff
>
>
> More permissions need to be granted to derbynet.jar in the server.policy
> file. David van Couvering reports that if you bring up the server and run the
> following command:
> java -jar derbyrun.jar server sysinfo
> then you get security exceptions as the sysinfo code, running inside the
> network jarball tries to read user.dir, user.home, user.name, java.home, and
> java.class.path.
> Kathey Marsden reports that if you try to run the network server with drda
> tracing turned on, then you get security exceptions when the server tries to
> open the trace log file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
