Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 5.1.1
-
Fix Version/s: 5.1.2
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
-
ICEsoft Forum Reference:
-
Support Case References:Support Case #13253 - https://icesoft.my.salesforce.com/5007000000zOLZG
Description
The file in question uses 128 bit RC4 AES encryption. For some reason the password callback is being fired by the security handler. Further investigation is needed.
After quite a bit of tracing it appears that we had an issue with how we are calculating the encryption key for v4 of the specification. The main issue was with regards to step 6 implementation or lack there of.
"If document metadata is not being encrypted, pass 4 bytes with the value of 0xFFFFFFFF to the MD5 hash, Security handlers of revision 4 or greater)"
Interestingly enough this bug has been around for quite some time.