-
-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Error code 2 using "7zz" - Fatal error #1443
Comments
Tested with 7zip output, same long password, no problems. |
@Inkoming just to be sure, what version of 7zip are you using? You mean 7-Zip on Windows? Or is it |
@aonez I'm on macOS, so only using Keka to compress to 7zip (no 7zip specific App). |
But this test you mentioned here with no problems, was it on macOS on the Terminal? Both |
The test with 7zip output (148 characters password) was through Keka on macOS, no Terminal. |
Ah ok you meant the 7Z format, got it. Seems like there's this 100 characters limit for ZIP + AES. Can you double check if it fails with lower character password on your end? You mentioned 49 characters but I'm unable to reproduce the issue with less than 100 characters. |
Tested right now, 99 characters ZIP 256 AES is working, above, not. My bad. |
Indeed. Just checked and WinZIP is limited to 99 characters, even for non AES256 passwords. So non AES compressed with 100+ characters can't be extracted using WinZIP.
That will be it. Thanks a lot for all the feedback @Inkoming. |
This was released with 1.4.0. Thanks again @Inkoming! |
Configuration
Describe the bug
Trying to compress little files with ZIP output using password (256 zip).
The password length is base64 148 characters using this format: Word---Word---Word (till 148 characters).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Keka should compress.
Screenshots
None.
Additional context
Changing the source folder doesn't change anything.
It looks like the problem is the password length.
Do we have a maximum password length? Please specify if it's the case.
Keka.log
The text was updated successfully, but these errors were encountered: