| Summary: | Ark : can't open password protected 7zip and RAR archives | ||
|---|---|---|---|
| Product: | [Applications] ark | Reporter: | the.tux.l33t |
| Component: | general | Assignee: | Harald Hvaal <metellius> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | 76jplvqw7t, ashl1future, chealer, doktor5000, egdfree, hugo.m.palma, isit81, lazy.kent, lukasas, manuel.neumann, rakuco, thstyl2000, valerio.passini, virgolus, zazy |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Bug Depends on: | |||
| Bug Blocks: | 469417, 35371 | ||
| Attachments: |
Sample of full encrypted 7z archive for Ark testing.
password: 123456
Sample of full encrypted RAR archive for Ark testing. password: 123456 |
||
|
Description
the.tux.l33t
2009-09-09 18:55:21 UTC
Can you attach sample 7zip and RAR files that do not work with their passwords? Created attachment 36840 [details]
Sample of full encrypted 7z archive for Ark testing.
password: 123456
Ark can't open and extract full encrypted 7z archive.
Created attachment 36841 [details]
Sample of full encrypted RAR archive for Ark testing.
password: 123456
Ark can't open and extract full encrypted RAR archive.
(In reply to comment #1) > Can you attach sample 7zip and RAR files that do not work with their passwords? OK, password: 123456 It seems that Ark have problems with full encrypted archives (RAR and 7zip "Encrypt file names" option). This archives request password, before viewing and extracting their contents. With normal encryption, Ark can open archive, and extract archive contents. *** Bug 188556 has been marked as a duplicate of this bug. *** OK, this is actually a generalization of bug 188556, which only mentioned header-protected RAR archives. Since this report is more general and contains attached test cases, I'm marking the other one as a duplicate of this one. Thanks! Isn't the problem "upstream"? I mean, how is Ark supposed to know that 7z wants a password if 7z just hangs prompting for input. There should be an option in 7z to make it return immediately if a password is needed. A workaround would be an "open with password" command in the Ark File menu (and/or in context menus). Ugly though. I'm looking into this bug because I find the "Encrypt file names" option quite useful. Same problem here....never managed to unpack any password protected rar file with ark....it works however smoothly using the command line.... Ark v2.14, KDE SC 4.4.2. Ark still doesn't open RAR archives with encrypted headers. ark still doesn't open passoword protected rar archives, this is ridiculous - this bug is rolling for almost a decade now kde 4.4.2, archlinux 2.6.33, ark 2.14, qt 4.6.2, unrar 3.93 i reproduce this bug. i use kde 4.4.2, ark 4.4.2, qt 4.6.2, unrar 3.90.4 *** Bug 234638 has been marked as a duplicate of this bug. *** *** Bug 235382 has been marked as a duplicate of this bug. *** For ark-kdeutils 3.X series submitted a patch. I know it is different program, but same logi may apply. See: http://bugs.pearsoncomputing.net/show_bug.cgi?id=181 Still no password suuport for 7z but header encrypted RARs now get correctly opened/extracted (ark kde3) Almost one full year and no solutions... neither an ugly one... nothing at all. These are things bringing people away from Linux and KDE. KDE packages quality is rapidly degrading :-( same problem. Ok i can use console and unrar program but is a big problem for newbie. Fileroller (gnome archive manager) work but i hate gtk program. Possibly this is duplicate of the bug 35371 (In reply to comment #16) > Fileroller (gnome archive manager) work but i hate gtk program. I don't get it. This bug has 265 votes, and is open for 9 months. And another FLOSS program gets it right, but Ark can't do the same? Could we pretty please get this fixed? Is this still open? If I try to open the attached samples the file content is not shown. There is also no question for the password. Sorry, I was mislead by the crossed out bug 35371 link. |