Skip to content
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

Cannot decrypt zip with "№" symbol in password #201

Open
Chocobo-ts opened this issue Apr 24, 2018 · 3 comments
Open

Cannot decrypt zip with "№" symbol in password #201

Chocobo-ts opened this issue Apr 24, 2018 · 3 comments

Comments

@Chocobo-ts
Copy link

Chocobo-ts commented Apr 24, 2018

Expected behaviour

Correct operation with any zip-passwords

Actual behaviour

ERROR: Wrong password when password contains or or

Steps to reproduce the behaviour

Create encrypted zip-archive with password contains symbol
Try to extract with engrampa, type password, getting error (wrong pass).

cli-utility unzip does this operations well, without errors

MATE general version

1.20.1

Package version

1.20.0

Linux Distribution

Debain Sid, also tested in ubuntu 16.04 and Linux Mint 18.3

@ghost
Copy link

ghost commented Aug 2, 2018

I can't reproduce that with the attached file.
Password is: №?or9℅=or-€
test.zip

@wigy-opensource-developer
Copy link

I am using Engrampa 1.26 in Ubuntu Mate 22.04.1 LTS jammy. I cannot encrypt or decrypt ZIP files using any password that contains non-ascii characters (á) either in Engrampa or the Caja plugin. I can use zip -re some.zip some/ with the same passwords though and I can also unzip them successfully. (Like the test.zip in the previous comment)

$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=hu_HU.UTF-8
LC_TIME=hu_HU.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=hu_HU.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=hu_HU.UTF-8
LC_NAME=hu_HU.UTF-8
LC_ADDRESS=hu_HU.UTF-8
LC_TELEPHONE=hu_HU.UTF-8
LC_MEASUREMENT=hu_HU.UTF-8
LC_IDENTIFICATION=hu_HU.UTF-8
LC_ALL=

@zhuyaliang
Copy link
Member

Please test if the issue still exists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants