Bug 132020

Summary: calc filesave password is limited to 15 characters when saving as xlsx
Product: LibreOffice Reporter: humphra <humphra>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aron.budea, miguelangelrv
Priority: medium    
Version: 6.1.5.2 release   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description humphra@gmx.fr 2020-04-10 10:40:05 UTC 
Description:
when i save a sheet in calc using the native ODS format i have no difficulties using a long password (in my case a password i cannot choose myself, long of 17 characters)
but when i try to save the same document in the xlsx format, i cannot enter the 17 characters, i can only enter 15.
This makes the situation very ennoying for me as my collegues have all the 17 characters password for working on those documents and most are using the microsoft office suite

Steps to Reproduce:
1.create a calc sheet
2.save as xlsx with password
3.enter a more than 15 character long password and you'll see the 16th... are not displayed in the password popup

Actual Results:
no way to enter a longuer than 15 character password saving as xlsx

Expected Results:
need to use a longuer password when saving as xlsx
work flawlessly !


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 6.1.5.2
Build ID: 1:6.1.5-3+deb10u5
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: fr-FR (fr_FR.UTF-8); Calc: group threaded
Comment 1 m_a_riosv 2020-04-10 11:02:15 UTC 
Works for me with
Version: 6.4.3.2 (x64)
Build ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8
CPU threads: 4; OS: Windows 10.0 Build 19592; UI render: GL; VCL: win; 
Locale: es-ES (es_ES); UI-Language: en-US Calc: threaded

Please test updating your LibreOffice version, 6.1 it's EOL and won't receive new patches.
Comment 2 Aron Budea 2020-04-10 11:03:41 UTC 
Looks like a dupe of bug 97086, which means it should be fixed since 6.4.0.

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