[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <905D612E-39EE-476D-BA81-2E467549CA9C@damienotis.link>
Date: Thu, 27 Aug 2026 14:20:57 -0700
From: Damien Otis <damien@...ienotis.link>
To: john-users@...ts.openwall.com
Subject: Re: need an ataxia mode
Hello,
> On 2026 Aug 26, at 23:18, Solar Designer <solar@...nwall.com> wrote:
>
> On Thu, Aug 27, 2026 at 07:34:55AM +0200, Solar Designer wrote:
>> On Wed, Aug 26, 2026 at 09:44:52PM -0700, Damien Otis wrote:
>>> The previous run returned a line:
>>> 1 0:00:00:00 - Algorithm: PBKDF2-SHA1 256/256 AVX2 8x
>>> I see 256. is AVX2 the specific instruction set for the standard sha 256?
>>
>> No. It just uses 256-bit vectors.
>>
>>> if I’m using openCL does the format change? I guess it wouldn’t be AVX2.
>>
>> Yes, this line wouldn't say AVX2 then.
>>
>> Far more importantly, why does this say PBKDF2-SHA1? This wouldn't be
>> the case for proper invocation on a "hash" produced by zip2john from a
>> zip archive, so you must have been running this incorrectly.
>
> Oh, sorry, I'm wrong. This is actually fine. I confused this line with
> a full format name and algorithm name line, but you took it from our log
> file where we have these on two different lines. The previous line
> probably said:
>
> 1 0:00:00:00 - Hash type: ZIP, WinZip (min-len 0, max-len 41 [worst case UTF-8] to 125 [ASCII])
>
> Did it?
Yes, the line before the one I included in my message says:
Hash type: ZIP, WinZip (min-len 0, max-len 106 [worst case UTF-8] to 319 [ASCII])
I don’t know which version of John I have; there seems to be no -v or version option, it’s not mentioned in the read me, but I can tell u I got the source from this github repository and built it myself: github.com/openwall/john
This is on Debian so I also installed some stuff via apt: build-essentials, zlib1g-dev, python-wheel-common, python3-wheel, libssl-dev, pkg-config, libgmp-dev, libkrb5-dev, libnss30dev, libz-dev, libbz2-dev, libpcap-dev, perl, libcpanplus-perl, cpanminus, python3-pip, python3-venv, nvidia-opencl-dev.
My zip2john command was: sudo $path_john_run/zip2john “$path_zip_source” > “$path_zip_hash”
The john command was something like: $path_john_run/john --min-length 8 --max length 8 --fork 14 “$path_zip_hash”
I ran it as a shell script, hence the variables. I hear that using a one-password word list with rules for oi would be the way to go, but perhaps I haven’t hashed the zip file correctly for AES 256? I didn’t use any arguments with zip2john.
> Alexander
Regards,
Damien
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.
