https://bugs.documentfoundation.org/show_bug.cgi?id=49697
Mike Kaganski <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|PDF: LO allows editing |PDF: LO asks for password |write-protected PDF when |opening attached file. |password field empty or |Evince does not. |clicking "Cancel" | --- Comment #31 from Mike Kaganski <[email protected]> --- (In reply to Mike Kaganski from comment #30) > Fixed by 2bbe15a2cea20d2dfb9346992a9bf8ff39b4d42c. Let me clarify. Quoting the current summary of the issue: > PDF: LO allows editing write-protected PDF when password field empty or > clicking "Cancel" This was set in comment 24 by stragu, with the stated rationale: > a PDF viewer opening the file is not a bug, but being able to edit the file > without giving the correct password is. Which is not correct. We do not edit PDFs. We have PDF only in Export dialog, not in Save (As); and that basically means, that application tells to users, that they import a PDF as Draw document, but when export the Draw document as PDF, they create a completely new document, unrelated to the original one - if it has the same name, it simply drops the old, and creates new. We do *not* claim we edit PDFs. If needed, we may want to emphasize it in the UI, but that is what it is. And additionally, *if* we ever make PDF filter the first-class filter, i.e. move it from export to save (as): then we need to treat the save protection the same way as we do for ODF. Save an ODF with only a password for editing (open file read-only + pw; no open password = no encryption), then open it. It will not ask any passwords on opening, and will just set the UI to read-only; this is what would have to happen here as well. The fix mentioned above just removed incorrect prompt, which was shown incorrectly - LibreOffice detected *a* protection, and assumed it needed to ask for password, and now it tests empty password from start, as it should. It completely resolves the original stated problem. So: restoring the original summary. Anything else needs own reports. -- You are receiving this mail because: You are the assignee for the bug.
