Bug 120857 - FILEOPEN DOC protected without pw can be edited
Summary: FILEOPEN DOC protected without pw can be edited
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:doc
Depends on:
Blocks: DOC-Doc-Protection
  Show dependency treegraph
Reported: 2018-10-24 06:31 UTC by Aron Budea
Modified: 2023-11-25 03:15 UTC (History)
0 users

See Also:
Crash report or crash signature:

Sample DOC, protected (29.00 KB, application/msword)
2018-10-24 06:31 UTC, Aron Budea

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2018-10-24 06:31:49 UTC
Created attachment 145956 [details]
Sample DOC, protected

The attached DOC has been created and set to protected in Word via Review -> Restrict Editing, with editing restrictions set to No changes (Read Only).
When opened in Writer, there's no editing restriction on the document.

With password set, there's a different issue, see bug 104494.

Observed using LO 6.2 alpha1 & 3.3.0 / Windows 7.
Comment 1 Dieter 2018-10-24 07:11:35 UTC
The document is opened in read-only mode, but you can choose "Edit document". In Word 2016 (German UI) I choose "Bearbeitung aktivieren" (Edit document?) and "Schutz aufheben" (disable protection?).

So for me it's not clear, waht do you expect in LO, Aron.
Comment 2 Aron Budea 2018-10-24 13:29:34 UTC
Thanks for checking, Dieter! For me in Writer it opens as editable, there's no editing restriction on the document, that is the problem.
Comment 3 Timur 2018-10-24 17:05:25 UTC
I confirm the report but I'm not sure this is different from Bug 104494. 
Because LO doesn't understand Restrict Editing and this is just another case, more simple one.
Comment 4 Aron Budea 2018-10-24 20:43:31 UTC
(In reply to Timur from comment #3)
> I confirm the report but I'm not sure this is different from Bug 104494. 
> Because LO doesn't understand Restrict Editing and this is just another
> case, more simple one.
Yes, I opened bug 120854 on the general support of this feature (ie. being able to adjust the settings in Writer in similar manner to Word, feature differences considered). Importing/exporting the setting is easier to support, and restricting editing to form fields is already supported, which is another subset of the feature. Otherwise I'm not sure how similar the issue is to bug 104494, the symptoms are rather different, that's why I decided opening a new ticket. Thanks for checking!
Comment 5 QA Administrators 2019-11-02 03:46:12 UTC Comment hidden (obsolete, spam)
Comment 6 Justin L 2020-03-09 11:27:25 UTC
Likely the issue is related to Dop2003's fTreatLockAtnAsReadOnly (1 bit): Specifies whether DopBase.fLockAtn means read-only
protection instead of protect for comments. By default, this value is 0.

I don't think we parse Dop2003, or anything newer than Dop97 actually (although mso-dumper.py recognizes up to Dop2007). There are lots of Dop20XXs. https://docs.microsoft.com/en-us/openspecs/office_file_formats/ms-doc/7ac3aac1-e3c9-4aff-a366-0d6f67ddb6fb
Comment 7 QA Administrators 2023-11-25 03:15:29 UTC
Dear Aron Budea,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team