https://bugzilla.redhat.com/show_bug.cgi?id=1540347 --- Comment #7 from Jaroslav Škarvada <jskarvad@xxxxxxxxxx> --- It seems there are more problems: $ hashcat -b hashcat (v4.0.1) 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. /usr/bin/OpenCL/: No such file or directory Started: Tue Feb 6 08:06:34 2018 Stopped: Tue Feb 6 08:06:34 2018 The OpenCL directory holds the so called OpenCL "kernels" so it has to be packed in the base package (and the devel subpackage should be dropped until upstream will come with the public headers for their API). Also the /usr/bin/OpenCL/ directory is not good for the OpenCL kernels. You should add the PREFIX to the build phase, i.e.: %make_build SHARED=1 DEBUG=1 PREFIX="%{_usr}" ... Then the hashcat will start looking for the kernels under: /usr/share/hashcat/OpenCL/ which is not the best, but much better than the /usr/bin Another problem is that hashcat then also needs: /usr/share/hashcat/hashcat.hctune /usr/share/hashcat/hashcat.hcstat2 BTW it seems hashcat.hcstat2 is LZMA packed data file,so that's why it bundles the LZMA_SDK. On my intel machine I had to force the OpenCL devices and then it started to do "something": $ hashcat -b --force hashcat (v4.0.1) 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. install_dir: /usr/bin, resolved_install_folder: /usr/bin /usr/share/hashcat clGetDeviceIDs(): CL_DEVICE_NOT_FOUND clGetDeviceIDs(): CL_DEVICE_NOT_FOUND OpenCL Platform #1: Intel ========================= * Device #1: Intel(R) HD Graphics Haswell Ultrabook GT2 Mobile, 1536/2048 MB allocatable, 20MCU OpenCL Platform #2: The pocl project ==================================== * Device #2: pthread-Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz, skipped. OpenCL Platform #3: Mesa, skipped or no OpenCL compatible devices found. Benchmark relevant options: =========================== * --force * --optimized-kernel-enable Hashmode: 900 - MD4 Speed.Dev.#1.....: 314.4 MH/s (66.18ms) Hashmode: 0 - MD5 Speed.Dev.#1.....: 201.4 MH/s (51.60ms) Hashmode: 5100 - Half MD5 Speed.Dev.#1.....: 126.3 MH/s (82.44ms) Hashmode: 100 - SHA1 Speed.Dev.#1.....: 35272.3 kH/s (73.79ms) Hashmode: 1400 - SHA-256 Speed.Dev.#1.....: 11895.5 kH/s (54.77ms) Hashmode: 10800 - SHA-384 ASSERTION FAILED: !(ctx->getErrCode() == OUT_OF_RANGE_IF_ENDIF && ctx->getIFENDIFFix()) at file /builddir/build/BUILD/Beignet-1.3.2-Source/backend/src/backend/gen_program.cpp, function virtual gbe::Kernel* gbe::GenProgram::compileKernel(const gbe::ir::Unit&, const string&, bool, int), line 248 Trasovací/ladící past (SIGTRAP) (core dumped [obraz paměti uložen]) Well, it's bad that it hung - we need to find out why from the coredump and probably address the problem upstream, but it's not blocker for the packaging. Also we should probably use: ExclusiveArch: %{ix86} x86_64 %{arm} in the spec file to limit the arches to x86 and arm only - I don't know much about OpenCL, but it still seems to be x86/arm specific (I haven't tried it on ARM, so I don't know whether it's usable there). But on ppc64: $ hashcat -b hashcat (v4.0.1) 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. Cannot find an OpenCL ICD loader library. You are probably missing the native OpenCL runtime or driver for your platform. * AMD GPUs on Linux require this runtime and/or driver: "RadeonOpenCompute (ROCm)" Software Platform (1.6.180 or later) * Intel CPUs require this runtime and/or driver: "OpenCL Runtime for Intel Core and Intel Xeon Processors" (16.1.1 or later) * Intel GPUs on Linux require this runtime and/or driver: "OpenCL 2.0 GPU Driver Package for Linux" (2.0 or later) * NVIDIA GPUs require this runtime and/or driver: "NVIDIA Driver" (367.x or later) So contrary to the hashcat-legacy which worked with the CPU, the new hashcat seems not to work without OpenCL, so it's probably useless to build it for architectures where OpenCL is not supported. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
