db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2196) Run standalone network server with security manager by default
Date Thu, 22 Feb 2007 15:34:06 GMT

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

Rick Hillegas updated DERBY-2196:
---------------------------------

    Attachment: secureServer.html
                derby-2196-10-renameOption-01.diff

Attaching derby-2196-10-renameOption-01.diff, which renames the -unsecure option to be -noSecurityManager
as Bernt and Andrew requested. Committed at subversion revision 510549. The unit tests ran
cleanly for me. I think that the compatibility tests should run cleanly too although I haven't
been able to run them because I don't have the 10.0.2.1 jars anymore.

Also attaching rev 7 of the functional spec. This incorporates two changes:

1) The change from -unsecure to -noSecurityManager

2) The change to the Basic policy, replacing the two codebase properties with a single property
which points to the directory of Derby jars


> 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, derby-2196-10-renameOption-01.diff,
secureServer.html, 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/%3c4582FE67.7040308@apache.org%3e
> 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.


Mime
View raw message