[DERBY-4493] encryptionAlgorithm is ignored at boot, but Documentation states it is required

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.5.3.0
• Fix Version/s: 10.10.1.1
• Component/s: Documentation
• Labels: derby_triage10_11
• Environment: Windows XP SP3 / JRE 1.5 / Derby 10.5.3.0 embedded.
• Urgency: Normal
• Bug behavior facts: Security
• Assignee: Unassigned
• Reporter: Sven Pedersen
• Created: 24/Dec/09 19:54
• Updated: 14/Nov/13 21:52
• Resolved: 01/Jul/13 14:30

Description

The documentation @ http://db.apache.org/derby/docs/10.5/devguide/tdevdvlp40140.html
states that

"If the algorithm that was used when the database was created is not the default algorithm, you must also specify the encryptionAlgorithm attribute"

yet when I gave the wrong value of "DES/CBC/NoPadding", having created the database with "DESede", it booted without a problem. I was concerned that it might not have actually encrypted with the correct algorithm, given this Java bug:
http://forums.sun.com/thread.jspa?threadID=5129170&start=15
I was concerned that it might not use strong (>128 bit) encryption. Other people may be similarly concerned about what the documentation seems to say, given the behavior of the code. I think that statement in quotes should be removed entirely, and one stating something to the effect of

"Just supply the bootPassword or encryptionKey attributes to boot the database."

Should replace it.

Issue Links

• relates to: DERBY-1721 DOCS - Remove duplicate information in Dev Guide re: Encryption