Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0 - Beta
-
Fix Version/s: 4.0 - Beta, 4.0
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:An encrypted PDF document.
Description
During testing, Mark identified two areas of concern when writing out encrypted pdf documents.
NameNode.decryptIfText(Object) :: line 136
- we create a new StringLiteral when decrypting a name tree node but don't copy the old parent reference neede for encryption.
URIAction.setURI(String) :: line 87
- uri was being saved a java.lang.String stead of StringObject.
NameNode.decryptIfText(Object) :: line 136
- we create a new StringLiteral when decrypting a name tree node but don't copy the old parent reference neede for encryption.
URIAction.setURI(String) :: line 87
- uri was being saved a java.lang.String stead of StringObject.
Issue Links
- blocks
-
PDF-72 PDF incremental updates
- Closed
The NameNode issue isn't to big a deal as we always save named references as Name object which aren't encrypted. However I did tidy up the code so we don't loose the object reference.
URIAction issue is definately a bug and would likely result in a URI that would be readable. I've update the code so that the save the URI value back to the URIAction dictionary as a StringObject. Encryption checks are now done on getURI():String call.