Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <7705928.1156180395864.JavaMail.jira@brutus>
Date: Mon, 21 Aug 2006 10:13:15 -0700 (PDT)
From: "Jean T. Anderson (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-1622) Add documentation for encrypted
 database using encryptionKey
In-Reply-To: <27654461.1154453894919.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]

Jean T. Anderson resolved DERBY-1622.
-------------------------------------

    Fix Version/s: 10.3.0.0
                       (was: 10.2.1.0)
       Resolution: Fixed
       Derby Info:   (was: [Patch Available])

Committed patch derby1622_devguide_5.diff  to trunk, revision 433290.

> Add documentation for encrypted database using encryptionKey
> ------------------------------------------------------------
>
>                 Key: DERBY-1622
>                 URL: http://issues.apache.org/jira/browse/DERBY-1622
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 10.2.1.0
>            Reporter: Sunitha Kambhampati
>         Assigned To: Laura Stewart
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: derby1622.diff, derby1622_2.diff, derby1622_3.diff, derby1622_4.diff, derby1622_devguide_5.diff, Derby1622_html.zip, derby1622_html2.zip, derby1622_html3.zip, derby1622_html4.zip, derby1622_html5.zip
>
>
> 1)
> In Reference Manual:Section: Setting attributes for the database connection url
> Add the following attribute:
> encryptionKey=key
> Function
> Specifies the key to use for encrypting a new database or booting an existing encrypted database. The application 
> provides the encryption key. 
> Combining with other attributes
> When creating a new database, must be combined with create=true and dataEncryption=true. When booting an existing 
> encrypted database, the encryptionAlgorithm is also required to be specified if the algorithm used when creating the 
> database was not the default algorithm. The default encryption algorithm used by Derby is DES/CBC/NoPadding.
> -- create a new, encrypted database
> jdbc:derby:newDB;create=true;dataEncryption=true;encryptionAlgorithm=DES/CBC/NoPadding;encryptionKey=6162636465666768
> -- boot an encrypted database
> jdbc:derby:encryptedDB;encryptionKey=6162636465666768
> 2)
> Developers Guide:
> http://db.apache.org/derby/docs/dev/devguide/tdevdvlp40140.html
> This should say , Booting an encrypted database.
> This section should also mention the encryptionKey attribute. 
> http://db.apache.org/derby/docs/dev/devguide/cdevcsecure60146.html 
> This section should also mention the encryptionKey attribute.
> Something like change this line from
> "Once you have created an encrypted database, you must supply the boot password to reboot it."
> to
> "If you have created an encrypted database using the bootPassword, then you  must supply the boot password to reboot it. If you have created an encrypted database using the encryptionKey, then you must supply the encryptionKey to reboot it"
> The example should also include the example to boot using the encryptionKey.
> For example, to access an encrypted database called encryptedDB, created with the encryptionKey c566bab9ee8b62a5ddb4d9229224c678 and with encryptionAlgorithm=AES/CBC/NoPadding, you would use the following connection URL:
> jdbc:derby:encryptedDB;encryptionAlgorithm=AES/CBC/NoPadding;encryptionKey=c566bab9ee8b62a5ddb4d9229224c678 

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