-
-
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
RAR password with symbols truncated #656
Comments
Hi @liushulun! I'm sorry I'm not familiar with the way Chinese characters are typed. What you need that Keka is lacking to write those characters? Maybe you can share a screencast showing what's needed? |
Keka always get error message when the password with Chinese character. |
Please @Gimmy1206 open a separate issue if you have trouble extracting a file. |
test.rar and test.7z all work. |
the password is this whole long line:
That's 196 characters, but 228 bytes. Success
Fail
|
Looking at rar command line closer, the problem for that tool is the space character in the last part of the password, meaning the password is not recognised as one string. If you remove the space character, or escape it with a preceding \ character, then the password is still valid and
Success
Fail
|
Looking further, it seems that the whole long password may not required to decrypt the rar? This password will extract the file using
Length: 127 characters, but 146 bytes. But this truncated password is not seen as valid for the other apps that previously extracted the file with the full password. I read the following:
So there are many issues at play here. I think support for longer password than the recommended spec varies by app. Solution use a password of 127 characters or less. |
Thanks for all the research and testing @gingerbeardman. You're right there, 127 truncated passwords. The other issue here is the symbol
Keka uses the later, thus it fails. BetterZip (and probably the others) use XADMaster so no parameter involved there. |
The symbols Here a build to test: Keka-v1.2.0-rc.1.r4158.7z |
Thanks! @aonez can fix this. |
Hi @aonez! Sorry for waiting so long. I got this problem that, when inputing password while extracting or encrypting, keka doesn't allow me to change my input source to chinese pinyin, so that I can only type english characters, like the two screenshots below: I can still copy the Chinese characters and paste into the edit box, but not convenient though. note: When typing password in Keka, [click caps-lock] would switch to uppercase, which should be switching input source as default shortcut on mac. Thus I guess Keka doesn't support typing the characters in other languages. Hope chinese characters inputing could be supported later~ |
@liushulun do other password fields in macOS allow switching input source? |
@gingerbeardman @liushulun just checked this is not possible in a standard password field. So I've created a new ticket to include an option to show the passwords (no using a secure field with asterisks) in #659. Since this ticked evolved in to a RAR password fix I'm closing it and the original Chinese characters question will be fixed in #659 😉 |
That reminds me, thx @gingerbeardman !!!
@aonez It will helps a lot! As far as I know, this is the common way in chinese extract/encrypt software. Thx !!! |
As a final followup, this is now also fixed in rarlab's Extracted from Version 6.00 beta 2
1. Bugs fixed:
a) Unix RAR version failed to correctly process manually entered
passwords if they did not exceed the maximum allowed 127 characters
in UTF-32 encoding, but exceeded this threshold in UTF-8. |
Another followup, in latest Version 6.10 beta 1
...
8. Warning is issued if entered password exceeds the allowed limit
of 127 characters and is truncated. Previously such passwords
had been truncated silently.
... So you all made this possible. |
Hi all, I'm so glad to have this utility on mac. But I'm wondering that, although compress / decompress with chinese character password is supported, I still need to copy the character from other place and paste into keka, it's somehow not convenient enough. And sometimes if I forget what I've copied, I'll have to check the content, that makes it low efficiency.
Looking forward to your reply~
The text was updated successfully, but these errors were encountered: