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 Tue, 18 Sep 2012 15:09:07 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

Attaching patch 1a (second round), which makes a series of boilerplate changes and does some
cleanup. Again, this patch shouldn't cause any functional changes.

Description:
 o DataFactory.setDatabaseEncrypted: introduced boolean flag to be able to tell the data factory
that encryption has been turned off
   Updated implementing method in BaseDataFileFactory
 o setDatabaseEncrypted: introduced second boolean flag to be able to tell the log factory
that encryption has been turned off
   Updated implementing methods in LogToFile and ReadOnly.
 o RawContainerHandle.encryptContainer: renamed to encryptOrDecryptContainer, added boolean
flag to control crypto operation
   Updated implementing method in BaseContainerHandle
 o BaseContainer.encryptContainer: renamed to encryptOrDecryptContainer, added boolean flag
to control crypto operation
   Updated implementing methods in RAFContainer and InputStreamContainer
 o EncryptData: renamed to EncryptOrDecryptData, added method decryptAllContainers, whitespace
changes
 o RawStore:
    - removed import
    - removed instance variable encryptDatabase
    - removed unused instance variable dataDirectory
    - renamed databaseEncrypted to databaseIsEncrypted
    - renamed configureDatabaseForEncryption to applyBulkCryptoOperation
    - made setupEncryptionEngines return a boolean: whether or not existing data must be transformed
(applyBulkCryptoOperation)
    - simplified parts of the logic in setupEncryptionEngines
    - introduced isTrue/isSet for property sets
    - removed unused method privList(File)

Patch ready for review.
Re-running regression tests.
                
> 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: 10.10.0.0
>            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

Mime
View raw message