You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2012/11/01 15:29:17 UTC

[jira] [Updated] (DERBY-5969) Encryption, re-encryption, and un-encryption silently fail if the database is already booted.

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

Rick Hillegas updated DERBY-5969:
---------------------------------

    Summary: Encryption, re-encryption, and un-encryption silently fail if the database is already booted.  (was: Re-encryption and un-encryption silently fail if the database is already booted.)
    
> Encryption, re-encryption, and un-encryption silently fail if the database is already booted.
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5969
>                 URL: https://issues.apache.org/jira/browse/DERBY-5969
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 10.10.0.0
>            Reporter: Rick Hillegas
>         Attachments: derby-5969-01-aa-warnEncryptionOnBootedDB.diff
>
>
> If the database is already booted, then the DBO's attempt to re-encrypt or un-encrypt the database will silently fail. It will appear to the DBO that the re(un)encryption succeeded but in fact the database will not be changed. Derby should raise an error if the database is already booted when the DBO attempts re(un)encryption.

--
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