Tilman Hausherr created PDFBOX-2888:
---------------------------------------
Summary: setAllSecurityToBeRemoved(true) before calling protect()
should have no effect
Key: PDFBOX-2888
URL: https://issues.apache.org/jira/browse/PDFBOX-2888
Project: PDFBox
Issue Type: Bug
Components: Crypto
Affects Versions: 2.0.0
Reporter: Tilman Hausherr
Assignee: Tilman Hausherr
Priority: Minor
Fix For: 2.0.0
As discussed on the mailing list:
user [~rnibali] had a problem where a file wasn't saved with encryption. The
cause turned out to be that he had called
{code}
setAllSecurityToBeRemoved(true)
{code}
and then
{code}
protect(...)
{code}
Although the javadoc of both methods is clear, I see a risk that this happens
again, e.g. when people combine existing code.
Solution: set allSecurityToBeRemoved to false when protect() is called and log
a warning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
