Bug 43229

Summary: Unable to un-protect password protected MS-Word .doc document
Product: LibreOffice Reporter: raymond
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: major CC: cedric.bosdonnat.ooo, jbfaure, LibreOffice, raymond, renato.mendes
Priority: medium Keywords: regression
Version: 3.5.0 RC2   
Hardware: x86 (IA32)   
OS: Linux (All)   
See Also: https://bugs.freedesktop.org/show_bug.cgi?id=45171
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 37361    
Attachments: password protected document

Description raymond 2011-11-24 11:28:13 UTC
Created attachment 53836 [details]
password protected document

1) Create new writer document, add some text
2) Save file (as Microsoft Word 97, don't know if this matters)
2a) check "Save with password", click "save"
2b) in the popup dialog, leave "File encryption password" empty
2c) Click "More options", click "Open file read-only
2d) "Enter password to allow editing"
3) Close file, re-open.


Expected behavior: 

Click "edit file" button. Enter password. Able to edit the document.


Actual behavior:

After password entry, the document is still read-only. No way to edit it.


Sample protected document attached. Password is "test".
Comment 1 Jean-Baptiste Faure 2012-01-28 14:34:08 UTC
I do not reproduce the problem with LO 3.4.5 But I reproduce it with LO 3.5.0 rc2+ (LibreOffice 3.5.0rc2+ Version ID : 20ec7c1-ed94322-5cd2479-2386a41-138191a)
under Ubuntu 11.10 x86_64.
So it is a regression. Changing version number and summary accordingly.

Best regards. JBF
Comment 2 Björn Michaelsen 2012-03-01 08:26:16 UTC
Likely the same root cause as https://bugs.freedesktop.org/show_bug.cgi?id=45171 if not a dupe.
Comment 3 Rainer Bielefeld Retired 2012-04-06 01:50:15 UTC
I believe this one is a DUP of "Bug 38147 - FILESAVE File Sharing Password protected MS Word document no longer editable after reopen"

@reporter:
Please feel free to reopen this Bug if you find evidence that we have an independent issue here.

*** This bug has been marked as a duplicate of bug 38147 ***