db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5792) Make it possible to turn off encryption on an already encrypted database.
Date Wed, 19 Sep 2012 10:56:08 GMT

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

Kristian Waagan updated DERBY-5792:

    Attachment: derby-5792-1a-boilerplate_and_preparation.diff

Not sure what went wrong, but the patch I uploaded was slightly outdated. While the correct
file was dated 16:57, the upload at 17:07 used an older version of the patch file. Maybe the
browser cached the older version, i.e. it read it before I pressed "Attach"?

I'm re-running the regression tests to verify that the errors go away.
> Make it possible to turn off encryption on an already encrypted database.
> -------------------------------------------------------------------------
>                 Key: DERBY-5792
>                 URL: https://issues.apache.org/jira/browse/DERBY-5792
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Store
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Kristian Waagan
>         Attachments: derby-5792-1a-boilerplate_and_preparation.diff
> Currently, you can encrypt an unencrypted database and you can change the encryption
key on an already encrypted database. However, Derby does not expose a way to turn off (unencrypt)
an already encrypted database.

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