db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5970) Check that connection attributes have legal values.
Date Wed, 21 Nov 2012 14:05:58 GMT

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

Knut Anders Hatlen commented on DERBY-5970:

territory: The reference manual says one place that it can be used on creation and on upgrade,
another place it says only on creation. I tried it and found that the territory attribute
had no effect on upgrade (will file a JIRA to fix the docs). If that's correct, we should
probably also raise a warning if territory is set on upgrade.
> Check that connection attributes have legal values.
> ---------------------------------------------------
>                 Key: DERBY-5970
>                 URL: https://issues.apache.org/jira/browse/DERBY-5970
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions:
>            Reporter: Rick Hillegas
>         Attachments: AttributeChecks.html, AttributeChecks.html, AttributeChecks.html,
derby-5970-01-aa-vetDecryptDatabaseValue.diff, derby-5970-01-ab-vetDecryptDatabaseValue.diff,
> At boot time, Derby does not check whether connection attributes are set to legal values.
This can cause them to be silently ignored. In the case of security operations like re(un)encryption,
these silent failures deceive the DBO into thinking that the security behavior of the database
has changed when, in fact, it hasn't. We should do the following:
> 1) Prevent decryptDatabase from being set to an illegal value. Since this is a new attribute,
there are no backward compatibility issues.
> 2) Evaluate other attributes on a case-by-case basis to determine which ones should raise
exceptions if they are set to illegal values. Technically, this may result in backwardly incompatible
behavior. However, I think that for most attributes, we will decide that the incompatibility
is minor and is a welcome bugfix.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message