Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 5.1.1
-
Fix Version/s: 6.1.3
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
-
ICEsoft Forum Reference:
Description
The file in question is prompting the user for a password. This doesn't appear to be the correct behavior. Further analysis is needed.
Activity
Patrick Corless
created issue -
Patrick Corless
made changes -
Field | Original Value | New Value |
---|---|---|
Fix Version/s | 6.1.3 [ 13086 ] |
Patrick Corless
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #49145 | Thu Sep 01 10:32:46 MDT 2016 | patrick.corless | |
Files Changed | ||||
MODIFY
/icepdf/branches/icepdf-6.1.0/icepdf/core/src/org/icepdf/core/pobjects/security/EncryptionDictionary.java
MODIFY /icepdf/branches/icepdf-6.1.0/icepdf/core/src/org/icepdf/core/pobjects/HexStringObject.java |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #49488 | Tue Nov 08 10:32:44 MST 2016 | patrick.corless | |
Files Changed | ||||
MODIFY
/icepdf/trunk/icepdf/core/src/org/icepdf/core/pobjects/HexStringObject.java
MODIFY /icepdf/trunk/icepdf/core/src/org/icepdf/core/pobjects/security/EncryptionDictionary.java |
Patrick Corless
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Took a while to track this one down but the issue was actually due to how we decode hex strings. The user password hash for this document started off with the 4 byte encoded string <FEFF...> which cause our hext string class to treat the string as a 4 byte encoded string instead of 2 byte. I refactored the hexString class to have a raw method so we can get at the 2byte values. There are are many examples of when 4 bytes are valid, this might be just a one off but the spec in this case tells use it should be 2 bytes.