Created attachment 99944 [details] word 2007 encrypted docx file - password is pass1234 After comment 1 of bug 76813, i decided to do some testing of password protected docx files from Word 2007, 2010 and 2013. The result is that on Linux Mint with the latest releases of LibO 3.6 - 4.2 and 4.3 beta, and none will open Word 2007 password encrypted files as it complains that the password is incorrect. If you click cancel, the file will load filled with characters like �, #, and >.
Confirmed in 4.2.4.2 and 4.3.0.0 beta1 on Ubuntu 14.04 - Set as New - Sophie
Thanks sophie. Also if you attempt to open protected file through the start center and click cancel, the mouse cursor will be stuck on busy.
I confirm this issue for Windows 8 Pro. With product 4.3.0.0 Beta 1.
Description: When i download this docx with password "pass1234", on the my computer, I click on the "Open" on the main menu of the program, When the "Password" field is shown, I put into this field "pass1234", but if i click on the "Ok" button, a message error is shown where i put a wrong password. If i click on the "Cancell" button, the document is showed, but there is a special characters. #####, bbbyyy. Step by Step: 1)I dowload this attachment into my computer 2)I load the my program 4.3.0.0 Beta 1 3)I click on the "File" menu where the program shows a submenu and i click on the "Open" 4)I choose the document protected by password 5)The document is loading but the program shows a new popup where I must enter a new password 6)I write this password "pass1234" and i click on the "Ok" button but the message shows is a wrong 7)If i click on the "Cancel" button, the document it's open but into the description there are different special characters like �, #, and >. SO:Windows 8 Pro Size Monitor:1366x768 Monitor: AMD Radeon HD 7670 Language: Italian/ all language Version document: 4.3.0.0 beta 1 Video: Video 1 => https://www.youtube.com/watch?v=HzMN4YAGxgg&feature=youtu.be
what program did you use for the recording Riccardo.
"pass1234" is not a correct password - MS Word 2013 also doesn't open the file with this password.
Just retested opening the file in word 2007 and 2010 and it opened fine. Tested it on word 2013 and it gave an open error.
(This is an automated message.) LibreOffice development currently prioritizes bugs with the so called MAB (most annoying bugs) -- as this bug has not run through that process (including writing a short rationale for this bug being a candidate and other who are watching the tracker bug silently approving that rationale etc.) its priority is set to high. Note this is effectively no change in the urgency assigned to this bug, as we are currently not making a difference between high and highest and severity is untouched. You can find out more about MABs and how the process works by contacting libreoffice qa on irc: http://webchat.freenode.net/?channels=libreoffice-qa The QA wiki page also gives you hints on how to get in contact with the team (if IRC fails you, your next best choice is the mailing list): https://wiki.documentfoundation.org/QA
I tried to unzip with unzip 6.0 and had this: Archive: test.zip End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of test.zip or test.zip.zip, and cannot find test.zip.ZIP, period. I can't unzip too on Win7 when just renaming the docx on zip. However, I can read the content with 7zip. But perhaps it shouldn't prevent LO to open this.
An encrypted Word 2007 document is a OLE storage which contains an (custom) encrypted ZIP file so no ZIP program should be able to unzip it. Interesting that you were able to read the content with 7zip.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Confirmed with v3.3.4 under windows 7 x64. Confirmed with v5.1.2.2 under ubuntu 14.04 x64.
Conforming with: Version: 5.3.0.0.beta1 Build ID: 690f553ecb3efd19143acbf01f3af4e289e94536 CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; Layout Engine: new; Locale: nl-NL (nl_NL); Calc: CL
I can confirm this bug. I created a password protected docx with LO and then find I can not open it again. Version: 4.2.8.2 Build ID: 420m0(Build:2) Using on Ubunty Trusty with KDE on a Chromebook (through crouton)
I'm unable to repo this anymore and newly created password protected files open fine in LO.