https://bugs.documentfoundation.org/show_bug.cgi?id=162138
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://ask.libreoffice.org | |/t/office-libre-draw-pdf-pr | |otection-not-working/98937/ | |10 CC| |[email protected] --- Comment #2 from V Stuart Foote <[email protected]> --- As you'd asked in your ASK note: "All I wanted to achieve is an easy, straightforards way to hide some information from and unskilled user without unnecessarily bloating or degrading an already existing PDF file (which originally was a scanned document in my case). No CIA-NSA-CSSS level of security." PDF is not intended to be an editable format. Even if we have created the PDF "roundtrip", we don't edit the PDF. Rather we parse its content using poppler libs (or pdfium just for conversion to full PDF sized image for now). We honor both User and Owner password when set on encrypted PDF--which we also apply on creation of an encrypted PDF--but we consume what poppler parses (and meets our needs for creating draw objects and text spans). We don't open a PDF read only--we either open it or we don't. The use case is to always open for import to Draw canvas page or Writer text document, or to insert as full PDF "page" images. And when we do we are taking an existing PDF through the LibreOffice Draw module by filter import, converting its content (images and any OCR text spans) into sd Draw objects. And if exporting back to PDF, those same Draw elements are written back into a PDF. As noted, and acknowledged by you in the Ask article, the "Redaction" feature for export to PDF performs the necessary masking of the document canvas as a "flattened" image--the underlaying content truly removed. There is no implementation error, we parse poppler lib filter streams as intended. And there is no use case in LibreOffice to do more with the limited 'print:' 'copy:' 'change:' 'addNotes:' document protection "encrypted" PDF provides--on import or export. (In reply to Buovjaga from comment #1) > > I confirm the reported issue of changes being allowed even though the > permission password dialog was dismissed. This is already seen in the first > version where PDF import worked, 3.6. isn't that bug 49697 -- You are receiving this mail because: You are the assignee for the bug.
