[
https://issues.apache.org/jira/browse/DERBY-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-5976:
-----------------------------
Attachment: DERBY-5976.zip
DERBY-5976.stat
DERBY-5976.diff
Thanks for the very clear spec, Rick! I'm attaching DERBY-5976.diff,
DERBY-5976.stat, and DERBY-5976.zip, which I hope make the suggested changes. I
made the language specific to each task.
M src/ref/rrefattribdecryptdb.dita
M src/ref/rrefattribnewencryptkey.dita
M src/ref/rrefattrib15290.dita
M src/ref/rrefattribnewbootpw.dita
M src/devguide/cdevcsecuredecryptdb.dita
M src/devguide/tdevcsecurenewextkey.dita
M src/devguide/tdevcsecurenewbootpw.dita
M src/devguide/tdevcsecureunencrypteddb.dita
> Document the new SQLWarning raised when trying to change the encryption state
> of an already booted database.
> ------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5976
> URL: https://issues.apache.org/jira/browse/DERBY-5976
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-5976.diff, DERBY-5976.stat, DERBY-5976.zip
>
>
> After committing derby-5969-01-aa-warnEncryptionOnBootedDB.diff, we will want
> to adjust the user guides to clarify the following point:
> o If you are changing the encryption state of the database, be sure to check
> for SQLWarnings after the change. The change succeeded only if there were no
> SQLWarnings or SQLExceptions.
> I think that the following sections need to be touched up:
> Developer's Guide:
> o "Encrypting an existing unencrypted database"
> o "Encrypting databases with a new boot password"
> o "Encrypting databases with a new external encryption key"
> o "Decrypting an encrypted database"
> Reference Manual:
> o "dataEncryption=true attribute"
> o "newBootPassword=newPassword attribute"
> o "newEncryptionKey=key attribute"
> o "decryptDatabase=true attribute"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
