[<prev] [next>] [day] [month] [year] [list]
Message-Id: <N1P-az613q30D1@Safe-mail.net>
Date: Fri, 14 Jun 2019 00:00:03 -0400
From: billwhittaker@...e-mail.net
To: john-users@...ts.openwall.com
Subject: Re: Unable to use OpenCL on arm64v8/debian stretch
> Also, are you able to use OpenCL on this system from any other program?
Further, pertinent information follows.
(1) from john-opencl-tester.tar.gz
./opencl-test.sh
Traceback (most recent call last):
File "opencl-generator.py", line 8, in <module>
from passlib.hash import md5_crypt as md5c
ImportError: No module named passlib.hash
Testing nt-opencl... Cracked :100
Testing phpass-opencl... Cracked :100
Testing cryptmd5-opencl... Cracked :100
Testing ssha-opencl... Cracked :100
Testing raw-sha1-opencl... Cracked :100
Testing raw-md5-opencl... Cracked :100
rm: cannot remove 'opencl-wordlist': No such file or directory
rm: cannot remove 'opencl-crack': No such file or directory
(2) My GPU only supports Open CL 1.1 1.2, but check out the last line from clinfo. Is it a problem?
clinfo
Number of platforms 1
Platform Name ARM Platform
Platform Vendor ARM
Platform Version OpenCL 1.2 v1.r14p0-01rel0-git(966ed26).f44c85cb3d2ceb87e8be88e7592755c3
Platform Profile FULL_PROFILE
...
CD loader properties
ICD loader Name OpenCL ICD Loader
ICD loader Vendor OCL Icd free software
ICD loader Version 2.2.11
ICD loader Profile OpenCL 2.1
(3) hashcat gives me the following gobbledygook, in particular, "Driver Version : 1.2". How can I tell/confirm if/that JtR is using the appropriate driver?
hashcat -I
hashcat (v5.1.0) starting...
OpenCL Info:
Platform ID #1
Vendor : ARM
Name : ARM Platform
Version : OpenCL 1.2 v1.r14p0-01rel0-git(966ed26).f44c85cb3d2ceb87e8be88e7592755c3
Device ID #1
Type : GPU
Vendor ID : 2147483648
Vendor : ARM
Name : Mali-T860
Version : OpenCL 1.2 v1.r14p0-01rel0-git(966ed26).f44c85cb3d2ceb87e8be88e7592755c3
Processor(s) : 4
Clock : 200
Memory : 229/919 MB allocatable
OpenCL Version : OpenCL C 1.2 v1.r14p0-01rel0-git(966ed26).f44c85cb3d2ceb87e8be88e7592755c3
Driver Version : 1.2
(4) Where JtR spits out an error, hashcat just hangs. (I gave it ~30+min).
hashcat -b -m 2500
hashcat (v5.1.0) starting in benchmark mode...
Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.
OpenCL Platform #1: ARM
=======================
* Device #1: Mali-T860, 229/919 MB allocatable, 4MCU
Benchmark relevant options:
===========================
* --optimized-kernel-enable
Hashmode: 2500 - WPA-EAPOL-PBKDF2 (Iterations: 4096)
(5) Following Alexander's suggestion and using github's JtR, I see, uh, uninspiring performance via OpenCL.
Any suggestions on making OpenCL functional?
../run/john --test --format=opencl
Device 1@...i: Mali-T860
Benchmarking: sha1crypt-opencl, (NetBSD) [PBKDF1-SHA1 OpenCL 4x]... DONE
Speed for cost 1 (iteration count) of 64000 and 40000
Raw: 6.3 c/s real, 914 c/s virtual
^CSession abortedPass-opencl [SHA256 AES/Twofish/ChaCha OpenCL]... ^CWait...
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.
