[
https://issues.apache.org/jira/browse/DERBY-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-5805:
-----------------------------
Attachment: DERBY-5805.zip
DERBY-5805.stat
DERBY-5805.diff
Attaching DERBY-5805.diff, DERBY-5805.stat, and DERBY-5805.zip, with revisions
to the encryption-related Reference Manual topics for completeness,
consistency, and formatting. The following files are changed:
M src/ref/rrefattrib88843.dita
M src/ref/rrefattribencryptkey.dita
M src/ref/rrefattribencryptkeylength.dita
M src/ref/rrefattribnewencryptkey.dita
M src/ref/rrefattrib15290.dita
M src/ref/rrefattrib42100.dita
M src/ref/refderby.ditamap
M src/ref/rrefattrib60346.dita
The only change in the map file was to correct the alphabetical order of a
couple of topics.
I hope no technical errors have been introduced. I don't know if the comments I
made in DERBY-4229 about the interaction of some of the attributes should have
any effect.
I will use DERBY-1721 to make fixes to Developer's Guide encryption topics.
Once these are all completed, I can add the decryption information as needed.
> Database encryption topics in Reference Manual need more information
> --------------------------------------------------------------------
>
> Key: DERBY-5805
> URL: https://issues.apache.org/jira/browse/DERBY-5805
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.9.1.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-5805.diff, DERBY-5805.stat, DERBY-5805.zip
>
>
> The Developer's Guide and Reference Manual information on the bootPassword
> and encryptionKey attributes doesn't state (not prominently, anyway) that
> these properties are mutually exclusive, as Rick Hillegas points out in his
> 6/8/2012 comment on DERBY-5622. This information should be included in the
> documentation for these properties.
> In general, the topics on database encryption attributes need additional
> information, corrections, and examples.
--
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
