db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-2409) Connecting to an already booted database with (re)encryption attributes gives no error or warning
Date Tue, 21 Feb 2012 07:52:32 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mike Matrigali updated DERBY-2409:

    Labels: derby_triage10_5_2 derby_triage10_9  (was: derby_triage10_5_2)

derby 10.9 triage.
> Connecting to an already booted database with (re)encryption attributes gives no error
or warning
> -------------------------------------------------------------------------------------------------
>                 Key: DERBY-2409
>                 URL: https://issues.apache.org/jira/browse/DERBY-2409
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:,,,,,,
>            Reporter: Dag H. Wanvik
>            Priority: Minor
>              Labels: derby_triage10_5_2, derby_triage10_9
>         Attachments: ij-repro.log
> If a database is shutdown and booted with (re)encryption,
> the (re)encryption boot will silently fail (i.e. no (re)encryption takes place), if another
> connection has booted the database in the meantime.
> Presumably, if the database was encrypted at creation time, only the dba will
> have the bootpassword and the above scenario is less likely.
> If it was created unencrypted, is is more of a hole, IMHO: Any other connection 
> can then foil the encryption boot, even one which can not be authenticated,
> cf DERBY-2407. To further exacerbate this issue; when the database is shutdown
> and rebooted, using the boot password supplied (and the database was not encrypted),
> no  error is given, since a boot password is not required. This can lull a dba
> into thinking the encryption took place! :( 
> We may want to generate a warning or an error in these cases.
> This issue may affect upgrade boots as well?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message