db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Thalamati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db
Date Mon, 19 Jun 2006 08:33:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1156?page=all ]

Suresh Thalamati updated DERBY-1156:
------------------------------------

    Attachment: reencrypt_3.diff

DERBY -1156 (partial)
This patch adds some code required to support reconfigure(rencryption) of
an already existing encrypted database with a new password(secret key)
or an external user specified encryption key. Two new attributes 
"newBootPassword" and "newEncryptionkey" are introduced to support this 
functionality. 

-- modified the code to support two have instance of two cipher 
   factories to exist. So that the existing data can decrypted with
   the old encryption key using one cipher factory and rewrite the data 
   with new encryption keys using another cipher factory. 

-- reenryption  of the database with new keys is similar to encrypting an already 
   existing database. All the container data is read through the page cache 
   and  rewritten using the new encryption keys. 

-- Added test case to test the re-encryption of an encrypted database.
 
TESTS : derbyall test suite passed on Windows XP/JDK142

It would be great if some can review this patch. 

svn stat:
M      java\engine\org\apache\derby\impl\services\jce\JCECipherFactory.java
A      java\engine\org\apache\derby\impl\services\jce\JCECipherFactoryBuilder.java
M      java\engine\org\apache\derby\impl\store\raw\RawStore.java
A      java\engine\org\apache\derby\iapi\services\crypto\CipherFactoryBuilder.java
M      java\engine\org\apache\derby\iapi\reference\Attribute.java
M      java\engine\org\apache\derby\iapi\reference\Module.java
M      java\engine\org\apache\derby\modules.properties
M      java\testing\org\apache\derbyTesting\unitTests\crypto\T_Cipher.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\store\encryptDatabaseTest1.sql
M      java\testing\org\apache\derbyTesting\functionTests\master\encryptDatabaseTest1.out


> allow the encrypting of an existing unencrypted db and allow the re-encrypting of an
existing encrypted db
> ----------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1156
>          URL: http://issues.apache.org/jira/browse/DERBY-1156
>      Project: Derby
>         Type: Improvement

>   Components: Store
>     Versions: 10.1.2.3
>     Reporter: Mike Matrigali
>     Assignee: Suresh Thalamati
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: encryptspec.html, reencrypt_1.diff, reencrypt_2.diff, reencrypt_3.diff
>
> encrypted database to be re-encrypted with a new password.
> Here are some ideas for an initial implementation.
> The easiest way to do this is to make sure we have exclusive access to the
> data and that no log is required in the new copy of the db.  I want to avoid
> the log as it also is encrypted.  Here is my VERY high level plan:
> 1) Force exclusive access by putting all the work in the low level store,
>    offline boot method.  We will do redo recovery as usual, but at the end
>    there will be an entry point to do the copy/encrypt operation.
> copy/encrypt process:
> 0) The request to encrypt/re-encrypt the db will be handled with a new set
>    of url flags passed into store at boot time.  The new flags will provide
>    the same inputs as the current encrypt flags.  So at high level the
>    request will be "connect db old_encrypt_url_flags; new_encrypt_url_flags".
>    TODO - provide exact new flag syntax.
> 1) Open a transaction do all logged work to do the encryption.  All logging
>    will be done with existing encryption.
> 2) Copy and encrypt every db file in the database.  The target files will
>    be in the data directory.  There will be a new suffix to track the new
>    files, similar to the current process used for handling drop table in
>    a transaction consistent manner without logging the entire table to the log.
>    Entire encrypted destination file is guaranteed synced to disk before
>    transaction commits.  I don't think this part needs to be logged.
>    Files will be read from the cache using existing mechanism and written
>    directly into new encrypted files (new encrypted data does not end up in
>    the cache).
> 3) Switch encrypted files for old files.  Do this under a new log operation
>    so the process can be correctly rolled back if the encrypt db operation
>    transaction fails.  Rollback will do file at a time switches, no reading
>    of encrypted data is necessary.
> 4) log a "change encryption of db" log record, but do not update
>    system.properties with the change.
> 5) commit transaction.
> 6) update system.properties and sync changes.
> 7) TODO - need someway to handle crash between steps 5 and 6.
> 6) checkpoint all data, at this point guaranteed that there is no outstanding
>    transaction, so after checkpoint is done there is no need for the log.
> ISSUES:
> o there probably should be something that catches a request to encrypt to
>   whatever db was already encrypted with.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message