[#DERBY-615] Get 95% of functional tests running under the SecurityManager when running derbyall

Derby

Get 95% of functional tests running under the SecurityManager when running derbyall

Created: 12/Oct/05 02:41 AM Updated: 01/Jul/09 12:04 AM

Return to search

Component/s:

Test

Affects Version/s:

None

Fix Version/s:

10.2.1.6

Time Tracking:

Not Specified

Issue Links:

Blocker

This issue is blocked by:

~~DERBY-626~~ Booting embedded engine requires read permission to derby.jar be granted for all code in the stack

~~DERBY-624~~ Running derbynetclientmats and derbynetmats requires accessDeclaredMembers permission to be granted with sane=true

Bug behavior facts:	Security
Resolution Date:	20/Jul/06 12:31 AM

Description

« Hide

Ensure that running derbyall tests all Derby's functionality works with a security manager and a correctly, minimally configured policy file. By minimally I mean just the fewset set of permissions required, hopefully in-line with the documentation. E.g. a policy file that allowed all permissions would work but would not be a good test of Derby.

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

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Daniel John Debrunner added a comment - 13/Oct/05 11:13 PM

Blocks ~~DERBY-615~~ because granting this permission so widely in the policy file has the potential to hide security bugs as more tests are enabled to be run under the security manager.

[ Permlink | « Hide ]

Daniel John Debrunner added a comment - 15/Oct/05 03:57 AM

Blocks 615 as without granting read permission to all code every test fails when run under the security manager, and granting such permission can hide bugs.

[ Permlink | « Hide ]

Daniel John Debrunner added a comment - 08/Apr/06 04:28 AM

As of 2006/0407 95.4% of tests in derbyall run under the security manager!!

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

I think I will keep this bug open until every test that does not run under the security manager has an open Jira
issue or valid reason in its _app.properties file.

[ Permlink | « Hide ]

Daniel John Debrunner added a comment - 20/Jul/06 12:31 AM

95+% tests run under the security manager, all tests with noSecurityManager=true have a valid reason, are blocked by a bug or a specific bug is entered to address the test.