Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <21195624.1179160636818.JavaMail.jira@brutus>
Date: Mon, 14 May 2007 09:37:16 -0700 (PDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2196) Run standalone network server with
 security manager by default
In-Reply-To: <4216116.1166553920991.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

    Attachment: releaseNote.html

Attach a second version of the release note in order to verfiy that the Release Note Generator picks up the latest version.

> 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
>             Fix For: 10.3.0.0
>
>         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, releaseNote.html, releaseNote.html, secureServer.html, secureServer.html, secureServer.html, secureServer.html, secureServer.html, secureServer.html, secureServer.html, secureServer.html, secureServer.html, secureServerReleaseNote.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.