[
https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578908#action_12578908
]
djd edited comment on DERBY-2109 at 3/14/08 12:56 PM:
------------------------------------------------------------------------
Guess it depends on the definition of painful? Be careful of using the tests as
an indicator of a typical application.
The required change, as far as I understand, is that an application that is
using system level authentication now needs to create its NetworkServerControl
objects with a user name and password, rather than with none. E.g. they need to
replace:
NetworkServerControl ctrl = new NetworkServerControl();
with
NetworkServerControl ctrl = new NetworkServerControl(user, password);
Or if they are using the command line, they need to add arguments
-user user -password password
I believe applications that do not use system authentication can continue to
use the NetworkServerControl constructors that do not take a user name &
password.
So are those two steps "painful" for an application picking up a new release of
its database engine which will close a security hole?
was (Author: djd):
Guess it depends on the definition of painful? Be careful of using the
tests as an indicator of a typical application.
The required change, as far as I understand, is that an application that is
using system level authentication now needs to create its NetworkServerControl
objects with a user name and password, rather than with none. E.g. they need to
replace:
NetworkServerControl ctrl = new NetworkServerControl();
with
NetworkServerControl ctrl = new NetworkServerControl(user, password);
Or if they are using the command line, they need to add arguments
-user user -password password
I believe applications that do not use system authentication can continue to
use the NetworkServerControl constructors that do not take a user name &
password.
> 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
> 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.
