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 "Sunitha Kambhampati (JIRA)" <de...@db.apache.org> on 2006/08/01 19:38:14 UTC
[jira] Created: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
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.0.0
Reporter: Sunitha Kambhampati
Priority: Minor
Fix For: 10.2.0.0
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
[jira] Resolved: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Andrew McIntyre resolved DERBY-1622.
------------------------------------
Resolution: Fixed
Derby Info: (was: [Patch Available])
> 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.2.1.0
>
> Attachments: derby1622.diff, derby1622_2.diff, derby1622_3.diff, derby1622_4.diff, Derby1622_html.zip, derby1622_html2.zip, derby1622_html3.zip, derby1622_html4.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
[jira] Assigned: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Laura Stewart reassigned DERBY-1622:
------------------------------------
Assignee: Laura Stewart
> 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.0.0
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.2.0.0
>
>
> 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
[jira] Commented: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=comments#action_12429119 ]
Sunitha Kambhampati commented on DERBY-1622:
--------------------------------------------
In my last comment ,
in #2 - Instead of "... and also the encryptionAlgorithm attribute if you want to use any other default algorithm"
I meant to say
"... and also the encryptionAlgorithm attribute if you want to use any algorithm other than the default"
Thanks.
> 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.2.1.0
>
> Attachments: derby1622.diff, derby1622_2.diff, Derby1622_html.zip, derby1622_html2.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
[jira] Closed: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Jean T. Anderson closed DERBY-1622.
-----------------------------------
Fix Version/s: 10.2.1.0
(was: 10.2.2.0)
Resolution: Fixed
> 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.2.1.0, 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
[jira] Commented: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=comments#action_12429138 ]
Sunitha Kambhampati commented on DERBY-1622:
--------------------------------------------
Thanks much Laura. I looked at files in derby1622_html4.zip and my +1 for commit.
> 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.2.1.0
>
> Attachments: derby1622.diff, derby1622_2.diff, derby1622_3.diff, derby1622_4.diff, Derby1622_html.zip, derby1622_html2.zip, derby1622_html3.zip, derby1622_html4.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
[jira] Commented: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=comments#action_12429448 ]
Sunitha Kambhampati commented on DERBY-1622:
--------------------------------------------
Thanks Laura for the updates. Changes in derby1622_html5.zip look good and can be committed.
> 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.2.1.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
[jira] Updated: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Laura Stewart updated DERBY-1622:
---------------------------------
Attachment: derby1622_html2.zip
derby1622_2.diff
Updated the patch based on your comments.
The updated/new files are:
Filename Topic title Action
tdevdvlp40140 Booting an encrypted database Added info about encryptionKey attribute
cdevcsecure60146 Booting an encrypted database Added info about encryptionKey attribute
tdevdvlpcreateencryptdbextkey Creating encrypted database with an external key New file
derbydev.ditamap Added new file and related links
The other files that are part of this patch but did not have any comments on them are (see comment on first patch for more info about these files):
rrefattribencryptkey
refderby.ditamap
> 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.2.1.0
>
> Attachments: derby1622.diff, derby1622_2.diff, Derby1622_html.zip, derby1622_html2.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
[jira] Updated: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Laura Stewart updated DERBY-1622:
---------------------------------
Derby Info: [Patch Available]
> 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.2.1.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
[jira] Updated: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Laura Stewart updated DERBY-1622:
---------------------------------
Derby Info: [Patch Available]
> 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.2.1.0
>
> Attachments: derby1622.diff, Derby1622_html.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
[jira] Commented: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=comments#action_12429070 ]
Sunitha Kambhampati commented on DERBY-1622:
--------------------------------------------
Thanks Laura for working on this.
Here are my comments on files in derby1622_html.zip.
FILE: /tdevdvlp40140.html
1)The below statement is not correct.
"
To boot an existing database:
In the URL, specify the encryptionKey and the bootPassword attributes for the encrypted database. For example:
jdbc:derby:encryptedDB;bootPassword=DBpassword;encryptionKey=6162636465666768
"
This needs to be changed to something like
To boot an existing encrypted database that was encrypted using the bootPassword mechanism, specify the bootPassword attribute.
For example:
jdbc:derby:wombat;bootPassword=clo760uds2caPe
To boot an existing encrypted database that was encrypted using an external key, specify the encryptionKey attribute.
For example:
jdbc:derby:flintstone;encryptionAlgorithm=AES/CBC/NoPadding;encryptionKey=c566bab9ee8b62a5ddb4d9229224c678
FILE : /cdevcsecure60146.html
1)Towards the end of the page, there is this line
"For example, the following connections would boot the database and thus require the boot password:"
This should change to account for the encryptionKey attribute also.
"For example, the following connections would boot the database and thus require the boot password or the encryptionKey depending on what mechanism was used to encrypt the database"
2)
"Note: The boot password is not meant to prevent unauthorized connections to the database after it has been booted"
This should also include the encryptionKey.
Note: The boot password or the encryptionKey is not meant to prevent unauthorized connections to the database after it has been booted
------------
I was looking a bit at derby-1636 and I realized that maybe we also need to have a link/section under 'Working With Encryption', something similar to 'Creating the boot Password'. in the developer's guide.
Creating encrypted database with external key.
To create an encrypted database using an external key, you can use the encryptionKey attribute as part of the connection url.
For example: To create an encrypted db 'encDB' using an external key
jdbc:derby:encDB;create=true;dataEncryption=true;encryptionAlgorithm=DES/CBC/NoPadding;encryptionKey=6162636465666768
Note: If you lose the encryptionKey you will not be able to boot the database.
> 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.2.1.0
>
> Attachments: derby1622.diff, Derby1622_html.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
[jira] Updated: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Laura Stewart updated DERBY-1622:
---------------------------------
Attachment: derby1622_3.diff
derby1622_html3.zip
Attaching the updated patch.
The files were updated based on comments received.
Please review and if you feel that is patch is ready for commit
add a comment with that statement.
Thanks!
> 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.2.1.0
>
> Attachments: derby1622.diff, derby1622_2.diff, derby1622_3.diff, Derby1622_html.zip, derby1622_html2.zip, derby1622_html3.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
[jira] Commented: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=comments#action_12430654 ]
Rick Hillegas commented on DERBY-1622:
--------------------------------------
Ported DERBY-1622 (433290, 432775) to 10.2 branch at subversion revision 436974.
> 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
[jira] Updated: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Jean T. Anderson updated DERBY-1622:
------------------------------------
Fix Version/s: 10.2.2.0
> 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, 10.2.2.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
Re: [jira] Updated: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Laura Stewart (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
>
> Laura Stewart updated DERBY-1622:
> ---------------------------------
>
> Attachment: derby1622_html5.zip
> derby1622_devguide_5.diff
>
> Updated file tdevdvlp40140 per comments received.
>
> I thought that file tdevdvlpcreateencryptdbextkey had been committed before, but when I do an SVN update, it appears that it didn't take from the last patch. So it appears in this patch.
I'll commit this.
-jean
[jira] Updated: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Laura Stewart updated DERBY-1622:
---------------------------------
Attachment: derby1622_html5.zip
derby1622_devguide_5.diff
Updated file tdevdvlp40140 per comments received.
I thought that file tdevdvlpcreateencryptdbextkey had been committed before, but when I do an SVN update, it appears that it didn't take from the last patch. So it appears in this patch.
> 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.2.1.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
[jira] Commented: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=comments#action_12429152 ]
Andrew McIntyre commented on DERBY-1622:
----------------------------------------
Committed derby1622_4.diff with revision 432775.
> 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.2.1.0
>
> Attachments: derby1622.diff, derby1622_2.diff, derby1622_3.diff, derby1622_4.diff, Derby1622_html.zip, derby1622_html2.zip, derby1622_html3.zip, derby1622_html4.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
[jira] Updated: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Laura Stewart updated DERBY-1622:
---------------------------------
Attachment: derby1622.diff
Derby1622_html.zip
Attached the patch to add the encryptionKey documentation.
Please review and comment.
The files added/updated are:
Filename Topic title Action
rrefattribencryptkey encryptionKey=<encryption key> New file
refderby.ditamap Updated
tdevdvlp40140 Booting an encrypted database Added info about encryptionKey attribute
cdevcsecure60146 Booting an encrypted database Added info about encryptionKey attribute
> 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.2.1.0
>
> Attachments: derby1622.diff, Derby1622_html.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
[jira] Reopened: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Jean T. Anderson reopened DERBY-1622:
-------------------------------------
Reopening to change fix version from 10.2.2.0 to 10.2.1.0. Jira will get updated with the right version number for the release version of 10.2.1.x.
> 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, 10.2.1.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
[jira] Closed: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Laura Stewart closed DERBY-1622.
--------------------------------
Closing this issue. Rick ported the patch(es) for this issue to the 10.2 branch on 8/26.
> 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, 10.2.2.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
[jira] Commented: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=comments#action_12429159 ]
Sunitha Kambhampati commented on DERBY-1622:
--------------------------------------------
Thanks Andrew for the commit.
There is one more small change needed.
In tdevdvlp40140.html
This last line is applicable to encryptionKey only. This line should be indented to fall under the last bullet.
"If the algorithm that was used when the database was created is not the default algorithm, you must also specify the encryptionAlgorithm attribute. The default encryption algorithm used by Derby is DES/CBC/NoPadding"
It would be great if this change can be made. Thanks.
> 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.2.1.0
>
> Attachments: derby1622.diff, derby1622_2.diff, derby1622_3.diff, derby1622_4.diff, Derby1622_html.zip, derby1622_html2.zip, derby1622_html3.zip, derby1622_html4.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
[jira] Resolved: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Commented: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=comments#action_12429117 ]
Sunitha Kambhampati commented on DERBY-1622:
--------------------------------------------
Hi Laura, Thanks for making the changes. They look good.
One minor comment, in the html file:/tdevdvlp40140.html, the third bullet looks misplaced.
There is some overlap between the derby-1636 changes and this one. As a result, I have some changes to the below file
FILE:rrefattribencryptkey.html
1)In Function:
Instead of the first two lines, please just add the below (which is similar to what is in bootPassword changes that you are doing for DERBY-1636)
Function:
Specifies the external key to use to :
* Encrypt a new database
* Configure an existing database for encryption
* Boot an existing encrypted database
2)heading: Combining with other attributes
Please add the following statement:
When you configure an existing database for encryption, the encryptionKey attribute must be combined with the dataEncryption=true attribute and also the encryptionAlgorithm attribute if you want to use any other default algorithm
Please add the following example
Examples:
-- configure an existing database for encryption
jdbc:derby:salesdb;dataEncryption=true;encryptionKey=6162636465666768
> 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.2.1.0
>
> Attachments: derby1622.diff, derby1622_2.diff, Derby1622_html.zip, derby1622_html2.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
[jira] Updated: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Laura Stewart updated DERBY-1622:
---------------------------------
Attachment: derby1622_4.diff
derby1622_html4.zip
Updated the files again.
> 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.2.1.0
>
> Attachments: derby1622.diff, derby1622_2.diff, derby1622_3.diff, derby1622_4.diff, Derby1622_html.zip, derby1622_html2.zip, derby1622_html3.zip, derby1622_html4.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
[jira] Reopened: (DERBY-1622) Add documentation for encrypted
database using encryptionKey
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ]
Laura Stewart reopened DERBY-1622:
----------------------------------
Need to add one more fix
> 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.2.1.0
>
> Attachments: derby1622.diff, derby1622_2.diff, derby1622_3.diff, derby1622_4.diff, Derby1622_html.zip, derby1622_html2.zip, derby1622_html3.zip, derby1622_html4.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