[
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
Attaching rev 5 of this spec. This makes the following changes based on my
experience in implementing the first piece of this work:
1) There is already a -b option. So I can't use that for printing out the Basic
policy. Instead, I have gone back to David's suggestion that we model
policy-printing as a separate command rather than a dash-option. This makes
more sense to me now that we only have a startup policy.
2) I had to broaden the socket accept privileges to all port numbers. This is
because, after accepting a connection request on the distinguished port, the
server then opens up a connection with the client on another port, whose number
is unpredictable.
> 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: 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.
