[ http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12429141 ] Suresh Thalamati commented on DERBY-1636: -----------------------------------------
My understanding of it is; 1) users need to disable log archival then do a shutdown before attempting to encrypt a database with a new key. So our example is not actually describing all the steps to do in this scenario. 2) This is not a necessary step for encrypting the database with a new key, it is more like recommendation. 3) and this is not a common case, our users rarely use log archival! I am ok, if you think it is better after the example as a seperate paragraph , but as a bullet point under "To encrypting a database with a new external key" does not seem right to me. > document encryption of an un-encrypted database and re-encryption with new > password/key. > ------------------------------------------------------------------------------------------ > > Key: DERBY-1636 > URL: http://issues.apache.org/jira/browse/DERBY-1636 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.2.1.0 > Reporter: Suresh Thalamati > Assigned To: Laura Stewart > Fix For: 10.2.1.0 > > Attachments: derby1636_devguide.diff, derby1636_devguide_html.zip, > derby1636_ref.diff, derby1636_ref_html.zip, reencrypt_devgudechanges.txt, > reencryptspec_1.html > > > document encryption of an un-encrypted database and re-encryption with new > password/key. -- 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
