When I was doing the classloader work, I had to grant permission to the Derby codebase to be able to do classloader-related work (createClassloader, accessClassInPackage.sun.reflect, getClassloader, getProtectionDomain).

How do I know whether granting a certain permission is shadowing a "bug" versus the right thing to do? I suspect what you want is as refined a policy as possible -- granting only the necessary permissions to the necessary jar file(s).

Also, if I need to grant new permissions, as above, what documentation do I need to change. Where is the "default policy file" that we ship to users (or does such a file not yet exist), as I would obviously need to modify this... Is derby_tests.policy being used as a template for this?

Thanks,

David



How should I fix this?  Should I edit a policy file or make a comment
to why it is disabled?


Depends on why it is failing. Adding policy file entries to work around
bugs is most likely a bad idea, it can hide other security bugs. If it's
the same reason as the other backup failures then add a comment with the
bug number. If it's a different reason then a new Jira bug report should
be entered and a comment to reflect that.


A related question: How is Derby users supposed to deal with this?  It
seems like it would create some hassle for them to run with the
SecurityManager.


Someone has to have the itch to fix the bug, otherwise it's broken for
the user.

It would be great for all the bugs I've found during this effort to be
fixed in the next release, I don't have time to fix them all.

http://wiki.apache.org/db-derby/SecurityManagerTesting

Thanks,
Dan.

begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard

Reply via email to