[
https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573921#action_12573921
]
Daniel John Debrunner commented on DERBY-2109:
----------------------------------------------
Committed (revision 632419) a sub-set of patch 12 related to the security code
without enabling any functionality.
Note that the SystemPrivilegesPermissionTest is not added into the _Suite (as
the complete patch does)
as I think it will fail under J2ME. It passes with classes but fails with jars
but that is to be expected
as the Derby's permissions classes are not yet added into the jars, this will
occur once they are used.
M java/build/org/apache/derbyBuild/classlister.java
D java/engine/org/apache/derby/authentication/DatabasePrincipal.java
A java/engine/org/apache/derby/authentication/SystemPrincipal.java
A java/engine/org/apache/derby/iapi/security
A java/engine/org/apache/derby/iapi/security/SecurityUtil.java
M java/engine/org/apache/derby/security/DatabasePermission.java
M java/engine/org/apache/derby/security/SystemPermission.java
M
java/testing/org/apache/derbyTesting/unitTests/junit/SystemPrivilegesPermissionTest.policy
M
java/testing/org/apache/derbyTesting/unitTests/junit/SystemPrivilegesPermissionTest.java
> 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.1.4
> Reporter: Rick Hillegas
> Assignee: Martin Zaun
> Attachments: DERBY-2109-02.diff, DERBY-2109-02.stat,
> derby-2109-03-javadoc-see-tags.diff, DERBY-2109-04.diff, DERBY-2109-04.stat,
> DERBY-2109-05and06.diff, DERBY-2109-05and06.stat, DERBY-2109-07.diff,
> DERBY-2109-07.stat, DERBY-2109-08.diff, DERBY-2109-08.stat,
> DERBY-2109-08_addendum.diff, DERBY-2109-08_addendum.stat, DERBY-2109-09.diff,
> DERBY-2109-09.stat, DERBY-2109-10.diff, DERBY-2109-10.stat,
> DERBY-2109-11.diff, DERBY-2109-11.stat, DERBY-2109-12.diff,
> DERBY-2109-12.stat, SystemPrivilegesBehaviour.html, systemPrivs.html,
> systemPrivs.html, 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.
-
You can reply to this email to add a comment to the issue online.
