db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2556) Code paths for db restore do not use doPrivileged-calls, causing SecurityException
Date Mon, 14 May 2007 07:33:17 GMT

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

Kristian Waagan resolved DERBY-2556.

    Resolution: Fixed

Committed 'derby-2556-4a_alternative-patch.diff' to trunk with revision 537735.

I ran derbyall/suites.All four times (once without DERBY-2555, the rest with). No failures
seen. I plan to commit DERBY-2555 tomorrow, after a tinderbox test has confirmed that this
patch is okay by itself. The tests were run with Sun JVMs 1.4, 1.5 and 1.6, all on Solaris
If the tinderbox fails again, there must be something funny going on with my environment.

Thanks for the additional work on the patch Kathey.

> Code paths for db restore do not use doPrivileged-calls, causing SecurityException
> ----------------------------------------------------------------------------------
>                 Key: DERBY-2556
>                 URL: https://issues.apache.org/jira/browse/DERBY-2556
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions:,
>         Environment: Derby running with a security manager.
>            Reporter: Kristian Waagan
>         Assigned To: Kathey Marsden
>             Fix For:
>         Attachments: derby-2556-2a_whitespace-javadoc.diff, derby-2556-3a_alternative-patch.diff,
derby-2556-3a_alternative-patch.stat, derby-2556-4a_alternative-patch.diff, derby-2556-4a_alternative-patch.stat,
derby-2556_diff.txt, derby-2556_stat.txt
> When using 'createFrom' or 'restoreFrom' in the JDBC url to restore a database from a
backup image, a SecurityException is thrown even though the policyfile for codebase derby.jar
is correctly configured (giving Derby access to the backup image).
> A few comments on this issue can be found here (and in subsequent comments): https://issues.apache.org/jira/browse/DERBY-1001#action_12439811
> A workaround is wrapping the connection call in doPrivileged at the "application-level
code", or granting the required permissions to the application codebase as well.

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

View raw message