Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 18 Sep 2020 18:40:23 +0100
From: Jasper Jones <>
Subject: Re: cracking encrypted zip file

No luck with the original session, unfortunately. I have a few other ideas
that I'll try in the coming days.

I also tried running JtR on the dummy file I posted earlier, running
--prince mode on the hash extracted with zip2john using a short list of
groups of characters from the password. It spat out the correct password in
a few seconds, so clearly it's all working as it should despite the error
message given by zip2john.

I may be back if I end up having to dig deeper into masks etc.  Thanks very
much for your patience and help.


On Thu, 17 Sep 2020 at 19:13, Jasper Jones <> wrote:

> That's interesting about running a different session, thanks Alexander.
> I'm sure no harm will come to my existing session, but given how long it's
> already been running, I'd like to minimise any chance of interruption. I'll
> definitely take a look at this once the current run finishes.
> Jasper
> On Thu, 17 Sep 2020 at 18:30, Solar Designer <> wrote:
>> On Thu, Sep 17, 2020 at 06:02:57PM +0100, Jasper Jones wrote:
>> > I've now tried zip2john with the zip file I just
>> > sent (attached again), and the result (test3.txt) is attached.
>> >
>> > I also got the following error message: ver 5.1 is not
>> > encrypted, or stored with a non-handled compression type".
>> Oh, that's great.  We'll look into it.
>> > I can't test whether the password can be cracked until the current run
>> > finishes.
>> Sure you can - use the "--session=test" option (or whatever name you
>> might like to give this new session).
>> Alexander

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.