[
https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463459
]
Daniel John Debrunner commented on DERBY-2109:
----------------------------------------------
Rick Hillegas (JIRA) wrote:
> 3) I split the Derby permission into 2 classes due to an inordinate fondness
> for modelling this on java.security.BasicPermission. I can abandon this
> attachment to BasicPermission in favor of something like this:
>
> permission org.apache.derby.security.SystemPermission "shutdownEngine";
> permission org.apache.derby.security.SystemPermission
> "${derby.system.home}${/}accountingDBA" "createDatabase";
Once you mention BasicPermission the split makes sense (ie. shutdownEngine does
not have an action), so adding more text around this in the functional spec
would be good. More along technical lines than "a fondness for" though :-)
Seems like the permission class for "createDatabase" should be
DatabasePermission, I could see this in the future being expanded to have
additional actions of "shutdown", "drop", "encrypt" etc. Then of course the
"createDatabase" action could be "create".
> 4) This spec does not cover and define the work for DERBY-2196. A separate
> spec has to be written for that JIRA. For the moment, let's imagine a spec
> for DERBY-2196 which follows the outlines of the wiki page linked from that
> issue. This spec (for DERBY-2109) then adds a delta on top of DERBY-2196: the
> addition of the Derby SystemPermissions to the Basic policy.
Ok - I think I get it. You writing this assuming that DERBY-2196 is done and
doesn't control system shutdown or database creation, and then this spec
describes how that basic policy would be changed by these permissions. Right?
Just hadn't thought of that order. :-)
One issue I see in the network server section is that it assumes a mapping
between the Java (OS) user name and the database user name. This would be a
first for Derby, no where else is such an assumption made.
I.e. ${user.name} is never used elsewhere in the code.
Not sure of the implications of this, or if there is a better user name to
grant shutdown system to for the basic policy.
> System privileges
> -----------------
>
> Key: DERBY-2109
> URL: https://issues.apache.org/jira/browse/DERBY-2109
> Project: Derby
> Issue Type: New Feature
> Components: Security
> Affects Versions: 10.3.0.0
> Reporter: Rick Hillegas
> Fix For: 10.3.0.0
>
> Attachments: systemPrivs.html, 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:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
