[<prev] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251220042401.GA22858@openwall.com>
Date: Sat, 20 Dec 2025 05:24:01 +0100
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: zip-opencl FAILED (crypt_all(1) = 0
Hi Daniel,
On Sat, Dec 06, 2025 at 06:47:44PM -0500, Daniel Isenberg wrote:
> My first question is if this is the correct way to ask questions/use the
> mailing list, but as that will likely answer itself, I'll move onto my next
> one.
Yes, it is the correct way, and I'm really sorry no one replied earlier.
> I've been trying to get the zip-opencl format to work on several AMD GPU's.
> (An R7 450 verde and some older Oland cards) but they fail. This is the
> output with verbosity set to 5:
>
> ./john --test=10 --format=zip-opencl --devices=1
> initUnicode(UNICODE, RAW/RAW)
> RAW -> RAW -> RAW
> 0: No OpenCL devices were found on platform #2: CL_DEVICE_NOT_FOUND (-1)
> Device 1: AMD Radeon (TM) R9 M360 (verde, LLVM 15.0.7, DRM 3.64,
> 5.15.0-163-generic)
> Benchmarking: ZIP-opencl, WinZip [PBKDF2-SHA1 OpenCL]... Loaded 4 hashes
> with 4 different salts to test db from test vectors
> Build time: 182.729 us
> LWS=256 GWS=256 (1 blocks) FAILED (crypt_all(1) = 0 for
> $zip2$*0*1*0*0675369741458183*5dc5*0**36b85538918416712640*$/zip2$)
>
> This looks a lot like https://github.com/openwall/john/issues/5709 however
> that workaround has been applied in the bleeding edge release that I am
> using. Instead of the output being (cmp_one(1)) in my case it
> is (crypt_all(1) = 0).
This looks like a similar kind of issue, but not the same - if you're in
fact already on a later code revision.
> Does anyone have any idea what the problem is or how I might fix it? I have
> a wide assortment of both nvidia and amd cards at my disposal. Could I
> contribute by running the --test=0 and making the results and other info
> available to the developers, and hopefully get my particular issue resolved
> in the process?
The problem is usually AMD drivers. The problem will almost certainly
go away if you move to an NVIDIA card. It may also go away if you move
to a different AMD driver and/or card... but you say you've already
tried several cards - was this all with the same driver? What driver
are you using? I do notice the device name string says "LLVM 15.0.7,
DRM 3.64", but these are just lower-level components perhaps in use by a
higher-level OpenCL backend/driver.
Yes, it will be mildly useful to us to have `--test=0` output for all
formats, along with information on your system software. You could open
a GitHub issue for that. It is unlikely we'll address such issues, but
at least we'll have a record of them.
Thank you!
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.
