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 Mon, 05 Feb 2007 17:08:05 GMT

     [ 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-01-print-01.diff

Attaching a patch for the first piece of this work. This patch implements the Network Server's
"policy" command, which prints out the Basic policy. Using this policy, I have successfully
brought the server up and down, created a database, and imported a jar file. This patch touches
the following files:

M      java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java
M      java/drda/org/apache/derby/loc/drda/messages_en.properties

Here is the Basic policy printed by the "policy" command:

grant codeBase "file:/export/home/rh161140/derby/mainline/trunk/jars/insane/derby.jar"
// These permissions are needed for everyday, embedded Derby usage.
  permission java.lang.RuntimePermission "createClassLoader";
  permission java.util.PropertyPermission "derby.*", "read";
  permission java.io.FilePermission "${derby.system.home}","read";
  permission java.io.FilePermission "${derby.system.home}${/}-", "read,write,delete";

// This permission lets you backup and restore databases
// to and from arbitrary locations in your file system.
// This permission also lets you import/export data to and from
// arbitrary locations in your file system.
// You may want to restrict this access to specific directories.
  permission java.io.FilePermission "<<ALL FILES>>", "read,write,delete";

grant codeBase "file:/export/home/rh161140/derby/mainline/trunk/jars/insane/derbynet.jar"
// This permission lets the Network Server manage connections from clients.
  permission java.net.SocketPermission "${derby.drda.host}:*", "accept"; 

> 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, 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
> By standalone I mean the network server was started though the main() method (command

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message