Oh... I am re-encrypting the loadNonSeq() document by using document.openProtection().... I'll stop that... Thanks!
On Wed, Feb 24, 2016 at 2:02 AM, Tilman Hausherr <[email protected]> wrote: > Am 24.02.2016 um 00:27 schrieb Brzrk One: > >> Yea, I think that's it. >> Comparing the input pdf to the loadNonSeq() output, I see objects that >> have the same content. >> This means that the loadNonSeq() output is encrypted - like the input - >> while the load() output is not. However, the loadNonSeq() output has no >> /Encrypt dictionary. >> >> I am using this on both paths: >> StandardDecryptionMaterial sdm = new StandardDecryptionMaterial(""); >> document.openProtection(sdm); >> > > You shouldn't use this on loadNonSeq, or in 2.0 (it isn't available there > anyway). > > You only need it with load() in 1.8. > > >> without error. >> Is this a feature of loadNonSeq() in the face of >> AccessPermission.canExtractContent() == true? >> Or did I do something wrong here? >> > > You need openProtection() only with load() in 1.8 and only if the file is > encrypted. (Yours is) > > Tilman >
