db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2109) System privileges
Date Fri, 29 Feb 2008 03:42:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573576#action_12573576

Myrna van Lunteren commented on DERBY-2109:

I ran derbyall, for starters, with my JSR169 implementation (the jvm available through IBM's
weme6.1) and unfortunately, this time, only 4 tests passed...(store/logDevice.sql; store/rollForwardBackup.sql,
store/backupRestore.sql, store/bootlock.java). 153 tests failed.

Many test diffs show something like this:
> Parsing policy file: file:C:/derbyt/svn/tst/j9_f11/d2109_12/derbyall/derby_tests.policy,
found unexpected: permission
and no connections are made (no database is created).

Here's one derby.log file example (again, lockTable) shows that this time it's the String.split
message which is not supported with JSR169 - at least, not with the implementation I'm using:

java.lang.NoSuchMethodError: java/lang/String.split(Ljava/lang/String;)[Ljava/lang/String;
	at org.apache.derby.security.DatabasePermission.initActions(DatabasePermission.java:237)
	at org.apache.derby.security.DatabasePermission.<init>(DatabasePermission.java:210)
	at org.apache.derby.impl.jdbc.EmbedConnection.checkDatabaseCreatePrivileges(EmbedConnection.java:2326)
	at org.apache.derby.impl.jdbc.EmbedConnection.createDatabase(EmbedConnection.java:2261)
	at org.apache.derby.impl.jdbc.EmbedConnection.<init>(EmbedConnection.java:354)
	at org.apache.derby.jdbc.Driver169.getNewEmbedConnection(Driver169.java:60)
	at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java:237)
	at org.apache.derby.jdbc.EmbeddedSimpleDataSource.getConnection(EmbeddedSimpleDataSource.java:406)
	at org.apache.derby.jdbc.EmbeddedSimpleDataSource.getConnection(EmbeddedSimpleDataSource.java:373)
	at java.lang.reflect.AccessibleObject.invokeL(AccessibleObject.java:213)
	at java.lang.reflect.Method.invoke(Method.java:272)
	at org.apache.derby.impl.tools.ij.util.getDataSourceConnection(util.java:426)
	at org.apache.derby.impl.tools.ij.util.startJBMS(util.java:516)
	at org.apache.derby.impl.tools.ij.util.startJBMS(util.java:585)
	at org.apache.derby.impl.tools.ij.ConnectionEnv.init(ConnectionEnv.java:64)
	at org.apache.derby.impl.tools.ij.utilMain.initFromEnvironment(utilMain.java:165)
	at org.apache.derby.impl.tools.ij.Main.<init>(Main.java:230)
	at org.apache.derby.impl.tools.ij.Main.getMain(Main.java:193)
	at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:178)
	at org.apache.derby.impl.tools.ij.Main.main(Main.java:73)
	at org.apache.derby.tools.ij.main(ij.java:59)

I'll kick off suites.All, to see what that shows us...

> System privileges
> -----------------
>                 Key: DERBY-2109
>                 URL: https://issues.apache.org/jira/browse/DERBY-2109
>             Project: Derby
>          Issue Type: New Feature
>          Components: Security
>    Affects Versions:
>            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.

View raw message