db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2196) Run standalone network server with security manager by default
Date Wed, 21 Feb 2007 21:42:05 GMT

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

Bernt M. Johnsen commented on DERBY-2196:
-----------------------------------------

The last paragraph in Andrew's last comment is DERBY-2363 (which I think is a good idea as
long as it is the client thet is negtiable on this, and not the server). But I do also think
that developers also need fingertip control in some environments. 

BTW: The flags for encryption on the wire (read SSL) as I plan to implement them is found
in the funcspec in DERBY-2356 (there are some changes from DERBY-2108). Seems that we need
some alignment here, so please comment.... Note also, that if the server is going to run with
SSL by default, the user will have to generate a public/private key pair before starting the
server (and no, I don't think supplying the key pair with the derby distribution is a good
idea since all an adversary needs to do to break the encryption then, is to get the private
key from the Derby download site).

> 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/%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