https://bugs.documentfoundation.org/show_bug.cgi?id=170808
Bug ID: 170808
Summary: Missing Password export when protecting a calc
sheet/table
Product: LibreOffice
Version: 26.2.0.3 release
Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: filters and storage
Assignee: [email protected]
Reporter: [email protected]
Description:
A Calc document with one sheet which is protected against editing with a
password (not the whole document but the one tablesheet) is exported to XLSX
without the password encryption hash in the XML Tag <spreadsheet protection
.../>. If you do so in Calc and analyse the XML Content of that sheet there is
a XML tag for the spreadsheet protection set to TRUE but without the given
password encryption hash, which you can observe in a similar produced original
XLSX out of Excel. The consequence is, that if you open this Calc produced XLSX
in Excel, the protection is set but without a password, you can unprotect it in
Excel easy without it. Even if you open the Calc produced XLSX in Calc, the
password is gone.
Interestingly the Excel produced XLSX with a password protected spreadsheet can
be opened in Calc and Calc respects the set password and ask for it and is
working well if given the password. So the technology for encrypt and decrypt
the password seems to be there.
Steps to Reproduce:
1.Produce a Calc document with one spreadsheet, protect the spreadsheet with a
password, export/save it as XLSX
2.Produce a Excel document with one spreadsheet, protect the spreadsheet with a
password, save it as XLSX
3.Analyse the XML code in both documents of the sheet in the tag <spreadsheet
protection ..../> and compare it
Actual Results:
different tag content, in Calc missing the hash for the password
Expected Results:
same XML tag in both documents, so that it is guranteed that the same bevaviour
with the password is given
Reproducible: Always
User Profile Reset: No
Additional Info:
see the attachments, one XLSX produced accordingly with Calc and one with Excel
for analysing them as mentioned
--
You are receiving this mail because:
You are the assignee for the bug.
