db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2109) System privileges
Date Mon, 11 Dec 2006 23:19:21 GMT
    [ http://issues.apache.org/jira/browse/DERBY-2109?page=comments#action_12457508 ] 
Daniel John Debrunner commented on DERBY-2109:

Rick thanks for writing this up and looking & proposing how to use the Java SecurityManager.

I would not have the fake concept of a " System Administrator ". With descriptions like this
it's better to be precise in the functional specification, maybe the user documentation could
explain it in more detail using the concept of a System Administrator.
e.g. in the functional spec replace sentances like this:

If the engine runs under a SecurityManager, then only a System Administrator can halt the

with the technially correct version of:

If the engine runs under a SecurityManager, then the shutdownEngine  DerbyPermission is required.

Since I assume since these are Java permissions that they can be granted to code as well as
Principles or are they restricted in some way? E.g. can I grant shutdown engine to all code?

I would not use DerbyPermission for the class name, the class name should describe permissions
it is covering, maybe
 org.apache.derby.security.SystemPermission ?

The code should not assume the Princple implementation is DerbyPrinciple, seems like it would
be useful to be able
to use other implementations of Principle. E.g. the existing UserAuthenticator class could
be expanded to have a new method
  public Principle getPrinciple(String userName)
allowing use of existing implementations such as X500Principal or the Principle implementation
returned from an LDAP setup.

Similar naming concerns for DerbyPrinciple, the class is already in the derby namespace so
it should be obvious that it's a Derby user, I think it's really something like:
   org.apache.derby.authentication.DatabasePrinciple ??

> System privileges
> -----------------
>                 Key: DERBY-2109
>                 URL: http://issues.apache.org/jira/browse/DERBY-2109
>             Project: Derby
>          Issue Type: New Feature
>          Components: Security
>    Affects Versions:
>            Reporter: Rick Hillegas
>             Fix For:
>         Attachments: systemPrivs.html
> Add mechanisms for controlling system-level privileges in Derby. See the related email
discussion at http://article.gmane.org/gmane.comp.apache.db.derby.devel/33151.
> The 10.2 GRANT/REVOKE work was a big step forward in making Derby more  secure in a client/server
configuration. I'd like to plug more client/server security holes in 10.3. In particular,
I'd like to focus on  authorization issues which the ANSI spec doesn't address.
> Here are the important issues which came out of the email discussion.
> Missing privileges that are above the level of a single database:
> - Create Database
> - Shutdown all databases
> - Shutdown System
> Missing privileges specific to a particular database:
> - Shutdown that Database
> - Encrypt that database
> - Upgrade database
> - Create (in that Database) Java Plugins (currently  Functions/Procedures, but someday
Aggregates and VTIs)
> Note that 10.2 gave us GRANT/REVOKE control over the following  database-specific issues,
via granting execute privilege to system  procedures:
> Jar Handling
> Backup Routines
> Admin Routines
> Import/Export
> Property Handling
> Check Table
> In addition, since 10.0, the privilege of connecting to a database has been controlled
by two properties (derby.database.fullAccessUsers and derby.database.defaultConnectionMode)
as described in the security section of the Developer's Guide (see http://db.apache.org/derby/docs/10.2/devguide/cdevcsecure865818.html).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message