Bug 140116 - XLS file not opening in Libo after encrypting it with Biff8 encryption in Apache POI
Summary: XLS file not opening in Libo after encrypting it with Biff8 encryption in Apa...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.2 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:xls
Depends on:
Blocks: Password-Protected MSO-External-Producers
  Show dependency treegraph
 
Reported: 2021-02-03 10:16 UTC by Ramakrishna
Modified: 2025-03-30 03:12 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
the password for this file is test123. Please open the file in MS office/Numbers, it works (7.50 KB, application/vnd.ms-excel)
2021-02-03 10:20 UTC, Ramakrishna
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ramakrishna 2021-02-03 10:16:09 UTC
Description:
Hi, I am using apache poi library to write an xls file and in some cases, also encrypting it using the method mentioned in http://poi.apache.org/encryption.html. But while opening this file in libo, it says wrong password, while the same file is opening just fine in MS Office.

Steps to Reproduce:
1.Create an xls file with data 
2.Protect the file with password using Biff8Encryption
3.Open the file with Libreoffice, it says The password is incorrect. The file cannot be opened

Actual Results:
Prompt is thrown saying The password is incorrect. The file cannot be opened

Expected Results:
File open fines in Ms Office, Numbers etc.


Reproducible: Always


User Profile Reset: No



Additional Info:
NA
Comment 1 Ramakrishna 2021-02-03 10:20:07 UTC
Created attachment 169419 [details]
the password for this file is test123. Please open the file in MS office/Numbers, it works
Comment 2 Roman Kuznetsov 2021-02-03 11:35:30 UTC
confirm problem in

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 6ab1feb2604d2620435a2aecbafff1d8c21255e9
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: threaded

and in

Версия: 5.2.7.2
ID сборки: 2b7f1e640c46ceb28adf43ee075a6e8b8439ed10
Потоков ЦП: 4; Версия ОС: Windows 6.2; Отрисовка ИП: по умолчанию; 
Локаль: ru-RU (ru_RU); Calc: group
Comment 3 Ramakrishna 2021-06-07 11:52:15 UTC
Roman Kuznetsov tested with LibreOfficeDev_7.2.0.0.alpha1_MacOS_x86-64 it still reproduces.
Comment 4 QA Administrators 2025-03-30 03:12:04 UTC
Dear Ramakrishna,

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

MassPing-UntouchedBug