Closed GoogleCodeExporter closed 9 years ago
Issue 212 has been merged into this issue.
Original comment by paracel...@gmail.com
on 20 Oct 2009 at 1:01
Issue 235 has been merged into this issue.
Original comment by paracel...@gmail.com
on 2 Feb 2010 at 5:15
Decompression of 7z archives doesn't recreate labels from the original!
Any comment?
Original comment by educ...@gmail.com
on 29 May 2010 at 4:07
I'm not sure what labels you mean. Also, that has nothing to do with encryption.
Rather, file a new issue, and provide a full explanation and a test file that
shows the problem.
Original comment by paracel...@gmail.com
on 29 May 2010 at 5:27
Could the opensource part of 7za for unarching with encryption be used? I
notice more and more folks using 7z and almost always with password.
Also, if the file extension is 000, 001 and split from a singular archive of an
encrypted 7z, unar refuses to even join. could this be modifed so hljoin isn't
required?
Original comment by atr000
on 24 Jun 2010 at 1:46
No, the code is far too different. It's not really hard to add support, though,
it's just a lot of work because 7zip supports too many different kinds of
encryption, just like everything else it does. I haven't bothered to work on it
since I have lots of other things I want more, and I never use encrypted 7z.
Adding support for multipart is pretty easy, but file a separate issue for it.
I need to know the exact naming schemes that are in use, though.
Original comment by paracel...@gmail.com
on 24 Jun 2010 at 1:55
[deleted comment]
[deleted comment]
It's a shame that support for opening encrypted 7z archives has been on the
back burner for 3.5 years now. Although the 7zip codec may support many types
of encryption, most of the OSX archivers I know of that can create 7z use
256-bit AES exclusively (Archiver, BetterZip, Compress Files, Entropy, Keka,
and 7zX -- I'm unsure about Compress and sArchiver because they're documented
poorly) so that's the only type that needs to be implemented.
At the least, this inability should be noted clearly on the Project Home page
so people are forewarned instead of having to discover it the hard way.
Presently, the text there implies that 7z is supported fully, which is
misleading.
Also, the program should give an accurate error message, e.g., "Cannot open
encrypted 7z files," instead of reporting that the file is corrupt.
Original comment by dpbas...@yahoo.com
on 25 Apr 2012 at 5:57
Well, it's been low priority due to the low likelihood of encountering these
files in the wild. I don't even have any samples, and I don't want to make my
own because then I just run into the trouble of there being too many to choose
from.
If you could collect sample files from various sources to give some kind of
baseline to work against that would be helpful to start with.
Original comment by paracel...@gmail.com
on 25 Apr 2012 at 10:42
I would kindly ask to support encrypted files, since more of them are appearing
lately.
This is my favourite program to view and extract archive files.
Look at my sample file below and see it doesn't even open (it says it's
corrupted, but it isn't).
Password: 123456789 (encrypted with 7z AES-256 bit)
Original comment by aky...@gmail.com
on 22 Sep 2012 at 4:38
Attachments:
Well, what I would need most of all is some idea of what exact crypto
algorithms are most used in the wild. Adding support for just those would be
fairly easy, if I knew which they are.
Original comment by paracel...@gmail.com
on 22 Sep 2012 at 4:47
Well, after doing a lot of digging through the 7zip source, I have implemented
SOMETHING which might work.
If anybody finds any 7z files which do not open once 3.5 is released, file a
new issue for those.
Original comment by paracel...@gmail.com
on 29 Oct 2012 at 1:14
Original issue reported on code.google.com by
paracel...@gmail.com
on 13 Dec 2008 at 11:54