[
https://issues.apache.org/jira/browse/DERBY-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-2196:
---------------------------------
Attachment: derby-2196-03-tests-01.diff
Attaching derby-2196-03-tests-01.diff. This is a unit test to verify that the
network server installs a security manager with the Basic policy as expected.
Makes the following changes:
M
java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/_Suite.java
Wires the test into the derbynet suite.
A
java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/SecureServerTest.java
The test itself. Tests that the server, when booted, installs a security
manager or not, depending on other command-line settings.
M java/testing/org/apache/derbyTesting/junit/NetworkServerTestSetup.java
Added some machinery for bringing the server up in a separate process. This
test needs a separate process to avoid having to poke special test
instrumentation into the network server itself.
M java/testing/org/apache/derbyTesting/junit/SecurityManagerSetup.java
M java/testing/org/apache/derbyTesting/junit/ServerSetup.java
M java/testing/org/apache/derbyTesting/junit/TestConfiguration.java
Made some machinery public.
> Run standalone network server with security manager by default
> --------------------------------------------------------------
>
> Key: DERBY-2196
> URL: https://issues.apache.org/jira/browse/DERBY-2196
> Project: Derby
> Issue Type: Improvement
> Components: Network Server, Security
> Reporter: Daniel John Debrunner
> Assigned To: Rick Hillegas
> Attachments: derby-2196-01-print-01.diff,
> derby-2196-01-print-02.diff, derby-2196-01-print-03.diff,
> derby-2196-02-install-01.diff, derby-2196-03-tests-01.diff,
> secureServer.html, secureServer.html, secureServer.html, secureServer.html,
> secureServer.html, secureServer.html
>
>
> From an e-mail discussion:
> ... Derby should match the security provided by typical client server
> systems such as DB2, Oracle, etc. I
> think in this case system/database owners are trusting the database
> system to ensure that their system cannot be attacked. So maybe if Derby
> is booted as a standalone server with no security manager involved, it
> should install one with a default security policy. Thus allowing Derby
> to use Java security manager to manage system privileges but not
> requiring everyone to become familiar with them.
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200612.mbox/[EMAIL
> PROTECTED]
> I imagine such a policy would allow any access to databases under
> derby.system.home and/or user.home.
> By standalone I mean the network server was started though the main() method
> (command line).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
