[
https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Zaun updated DERBY-2109:
-------------------------------
Attachment: DERBY-2109-05and06.diff
DERBY-2109-05and06.stat
Hi Rick,
I could not reproduce that patch issues you reported: I checked out a clean
trunk, downloaded and applied patch 05 (patch -p0 < DERBY-2109-05.diff), then
-06; no problems during patch and build. These two patches should be
independent from each other, and a quick look didn't reveal any overlapping
code to me.
However, as a cross-check, I've attached a combined patch
DERBY-2109-05and06.diff (from the freshly patched trunk) and hope this one
works better.
About the patches' status, yes, I consider patch:
- DERBY-2109-05.diff, which contains the System Privileges enforcement code,
ready for discussion (expecting questions), and
- DERBY-2109-06.diff, which contains some System Privileges unit test fixes,
ready for commital (or discussion if there are any questions). The unit test
(suite) runs fine in my freshly patched and build trunk:
java -cp
"jars/sane/derbynet.jar;jars/sane/derby.jar;tools/java/junit.jar;jars/sane/derbyTesting.jar;"
junit.textui.TestRunner org.apache.derbyTesting.unitTests.junit._Suite
If you find the unit test's two println()s unecessary, please, feel free to
remove them:
testing System Privileges ...
testing System Privileges: done.
About the SystemPrivilegesTestCases.html document, I'll break out the "invalid
credentials" case into two lines with a few updates (right after my return in a
week).
Thanks for your comments so far, Martin
> 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-05.diff, DERBY-2109-05.stat, DERBY-2109-05and06.diff,
> DERBY-2109-05and06.stat, DERBY-2109-06.diff, DERBY-2109-06.stat,
> SystemPrivilegesTestCases.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.
