https://bugs.documentfoundation.org/show_bug.cgi?id=149621
--- Comment #5 from S.B. <quick_web_design_to...@hotmail.com> --- Unfortunately it has been a really long time since I last programmed anything and my language of choice was Delphi (Turbo Pascal). It would take me a long time to get up to speed on this by myself. My thoughts are that "encryption" should not necessarily indicate that a file should be unreadable without a password, only that it may have levels for access based upon editor access permissions and viewer access permissions. If it is not determining the difference between the different permission types and levels of access and just lumping all under "encrypted" and requiring all levels to enter a password rather than allowing an access level to be chosen (which should then request a password based upon access rights) then something has not been coded properly. The encryption is basically prevention of editing contents without editing rights. If general read permissions are allowed in the file, then decryption of the contents for read only purposes should be automatic (Gimp's behaviour?), while editing permission should then require the editor's password. (eg. expected behaviour would be - when someone tries to type in the document a dialogue should come up requesting the editor's password *OR* a notice to indicate that the file is "read only".) Without actually seeing the PDF specifications, I am going to assume that permissions should be like this: Open (editable) Read Only (Viewable but not editable without editor password) Private (Not viewable without read password but editable once viewable) Private Read Only (Not viewable without Read password Not editable without editor password) Anything Read Only or above will contain encryption. So maybe there is a section in the specification on access permissions? -- You are receiving this mail because: You are the assignee for the bug.
