You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <de...@db.apache.org> on 2006/03/06 14:05:32 UTC
[jira] Updated: (DERBY-623) Derby monitor accesses two system
properties without using a privileged block when built sane=true
[ http://issues.apache.org/jira/browse/DERBY-623?page=all ]
Kristian Waagan updated DERBY-623:
----------------------------------
Attachment: DERBY-623-2a-javadoc.stat
DERBY-623-2a-javadoc.diff
A separate patch ('DERBY-623-2a-javadoc.diff') for a few Javadoc fixes. First, a spelling error is corrected several places ('privledged' -> 'priviledged') and the prefix for properties have been changed from 'db2j' to 'derby.' (only documentation is changed in this patch, implementation is untouched).
A committer should be able to both review and commit this small patch (8 lines changed).
DERBY-623-2a-javadoc.diff does not resolve this issue, it is only an additional documentation fix.
> Derby monitor accesses two system properties without using a privileged block when built sane=true
> --------------------------------------------------------------------------------------------------
>
> Key: DERBY-623
> URL: http://issues.apache.org/jira/browse/DERBY-623
> Project: Derby
> Type: Bug
> Components: Services
> Versions: 10.2.0.0
> Reporter: Daniel John Debrunner
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: DERBY-623-2a-javadoc.diff, DERBY-623-2a-javadoc.stat
>
> When built with sane=true and testing with the jars these permissions are required to be granted all the way up the stack, currently this means for the tests granting them to the network server jar.
> permission java.util.PropertyPermission "derby.monitor.verbose", "read";
> permission java.util.PropertyPermission "derby.debug.*", "read";
> The engine contains code to read system properties using privileged blocks, this should be used by the monitor.
--
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