Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 13 Jun 2019 22:30:54 -0400
From: billwhittaker@...e-mail.net
To: john-users@...ts.openwall.com
Subject: Re: Unable to use OpenCL on arm64v8/debian stretch

> > >When I run, as in README-OPENCL,
> > >../run/john --test --format=wpapsk-opencl
> 
> What happens if you test another format, e.g. md5crypt-opencl, or try
> testing them all with "--format=opencl"?  This will tell us whether the
> problem is format-specific or not.

../run/john --test --format=md5crypt-opencl
Device 1@...i: Mali-T860
Benchmarking: md5crypt-opencl, crypt(3) $1$ [MD5 OpenCL]... 0: OpenCL CL_INVALID_EVENT_WAIT_LIST (-57) error in opencl_common.c:1794 - clWaitForEvents

> 
> Also, are you able to use OpenCL on this system from any other program?
> 
> > >../run/john --test --format=wpapsk-opencl --device=0

I've installed hashcat, and it hangs for 30min+ on a test of the same format. So, no.
Can you suggest any other program? Or is this negative result sufficient to show that, I suppose, OpenCL on the system, with or without pocl (which I installed subsequently), is somehow deficient?

> > Before we even start to think about that, you need to upgrade to latest 
> > release, which is 1.9.0-jumbo-1. If you still have problems after that, 
> > please repost.
> 
> magnum, I see no reason to think the above wasn't already with
> 1.9.0-jumbo-1.  In fact, the mention of "ASIMD" suggests it was with a
> revision very close to 1.9.0-jumbo-1 even if not the release exactly.
> (We sort of mistakenly reported Aarch64's SIMD as NEON before.)

I cloned from github ~18hrs ago.
My procedure follows.
     apt-get install ocl-icd-libopencl1 clinfo libopenmpi2 openmpi-bin argon2
The following additional packages will be installed:
  libgfortran3 libhwloc-plugins libhwloc5 libibverbs1 openmpi-common

     an installation of rexgen followed by running ldconfig, and then,

     git clone git://github.com/magnumripper/JohnTheRipper -b bleeding-jumbo john

     apt-get libssl-dev yasm libgmp-dev libpcap-dev libbz2-dev zlib1g-dev libopenmpi-dev openmpi-bin libgmpxx4ldbl libpcap0.8 libpcap0.8-dev libhwloc-dev libibverbs-dev libltdl-dev libnuma-dev opencl-c-headers libzip-dev libzip4
      cd john/src
      ./configure --enable-mpi
      make -s clean && make -sj6
      ../run/john --test=0 --format=cpu
Testing: crypt, generic crypt(3) [?/64]... (6xOMP) PASS
All 404 formats passed self-tests!

Incidentally, I am working on a Rock Pi. When I run the binary compiled on a Rock64, I see,
All 705 formats passed self-tests!
When I compile from the (older bleeding) source for this JtR, I see
All 403 formats passed self-tests!

Why am I seeing different quanties of formats?

Powered by blists - more mailing lists

Your e-mail address:

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