https://bugs.documentfoundation.org/show_bug.cgi?id=169375

            Bug ID: 169375
           Summary: Password protected section is not really "password
                    protected" if you save and reopen a *.docx file.
           Product: LibreOffice
           Version: 7.3.7.2 release
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
If you create a *.docx file and password protect a created section, the
protection only works as long as the file remains open. If you save it and
reopen it you can very easily remove the tic mark and un-protect the section
without entering a password! :)

Steps to Reproduce:
1.create a text file.
2.select a paragraph write click and edit section
3.Under "write protection" tick "protect" and tick "with password"
4.Insert and confirm your password
5.click "OK" and try to modify the protected section. A popup "Read only
content" appears. 
6.Try to edit again the section and remove the protection. It will ask for the
password.
7.Save as .docx and reopen the file.
8.Go to the protected section.
9. Right click and "edit section"
10. You can remove the "protect" tick without being asked to insert the
password

-----THE ABOVE STEPS DO NOT APPLY FOR AN .odt FILE------

Actual Results:
the "protected" section in a .docx file is no longer protected if you reopen
the file

Expected Results:
It should password protect the section in any case and ask for the password
every time someone opens the file and tries to edit the specific section


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.3.7.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.10
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to