[DERBY-5969] Encryption, re-encryption, and un-encryption silently fail if the database is already booted.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.10.1.1
• Fix Version/s: 10.10.1.1
• Component/s: Services
• Labels: derby_backport_reject_10_9
• Issue & fix info: Release Note Needed, Repro attached
• Bug behavior facts: Security
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 29/Oct/12 17:54
• Updated: 27/Jun/13 22:42
• Resolved: 27/Jun/13 22:42

Description

If the database is already booted, then the DBO's attempt to re-encrypt or un-encrypt the database will silently fail. It will appear to the DBO that the re(un)encryption succeeded but in fact the database will not be changed. Derby should raise an error if the database is already booted when the DBO attempts re(un)encryption.

Issue Links

• is duplicated by: DERBY-2409 Connecting to an already booted database with (re)encryption attributes gives no error or warning
• is related to: DERBY-5976 Document the new SQLWarning raised when trying to change the encryption state of an already booted database.
• relates to: DERBY-5968 A failed connection attempt may nevertheless manage to boot the database.
• relates to: DERBY-2409 Connecting to an already booted database with (re)encryption attributes gives no error or warning
• relates to: DERBY-5792 Make it possible to turn off encryption on an already encrypted database.