+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: m13600 error,Self-test hash parsing error: Token encoding exception (/thread-8746.html)
m13600 error,Self-test hash parsing error: Token encoding exception - sdwzzx - 10-30-2019
Hello All
Thank you to see my post.
I want to crack a winzip file,I use the zip2john to get the hash,and my zipfile is about 2K
I run the cmd below:
Quote:./hashcat-5.1.0/hashcat -m 13600 zip-test.txt -a 3
and get the error
Quote:john@ubuntu:~/crack$ ./hashcat-5.1.0/hashcat -m 13600 zip-test.txt -a 3
hashcat (v5.1.0) starting...
OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: gfx900, 6949/8176 MB allocatable, 56MCU
Hashfile 'zip-test.txt' on line 2 ($pkzip...494dca8f344266b1dc4392*$/pkzip2$): Signature unmatched
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
* Slow-Hash-SIMD-LOOP
Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256
Watchdog: Temperature abort trigger set to 90c
clBuildProgram(): CL_BUILD_PROGRAM_FAILURE
lld: error: undefined hidden symbol: sha1_update_64
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_comp)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_comp)
lld: error: undefined hidden symbol: sha1_final
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_comp)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-9b5bb2/input/linked.bc.o(m13600_comp)
Error: Creating the executable from LLVM IRs failed.
* Device #1: Kernel /home/john/crack/hashcat-5.1.0/OpenCL/m13600-pure.cl build failed - proceeding without this device.
Then I run the -b command
Quote:john@ubuntu:~/crack$ ./hashcat-5.1.0/hashcat -b -m 13600Also the same error
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: Advanced Micro Devices, Inc.
================================================
* Device #1: gfx900, 6949/8176 MB allocatable, 56MCU
Benchmark relevant options:
===========================
* --optimized-kernel-enable
Hashmode: 13600 - WinZip (Iterations: 1000)
clBuildProgram(): CL_BUILD_PROGRAM_FAILURE
lld: error: undefined hidden symbol: sha1_update_64
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_comp)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_comp)
lld: error: undefined hidden symbol: sha1_final
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_init)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_comp)
>>> referenced by /home/john/crack/hashcat-5.1.0/OpenCL/comgr-f6c8b0/input/linked.bc.o(m13600_comp)
Error: Creating the executable from LLVM IRs failed.
* Device #1: Kernel /home/john/crack/hashcat-5.1.0/OpenCL/m13600-pure.cl build failed - proceeding without this device.
Started: Wed Oct 30 11:08:59 2019
Stopped: Wed Oct 30 11:09:02 2019
Then I try the beta one:
Get this error
Quote:john@ubuntu:~/crack$ ./hashcat-5.1.0-beta/hashcat.bin -b -m 13600
hashcat (v5.1.0-1403-g87022919) 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.
/home/john/crack/hashcat-5.1.0-beta/OpenCL/m13600-optimized.cl: Optimized kernel requested but not needed - falling back to pure kernel
OpenCL API (OpenCL 2.1 AMD-APP (2982.0)) - Platform #1 [Advanced Micro Devices, Inc.]
=====================================================================================
* Device #1: gfx900, 6949/8176 MB allocatable, 56MCU
Benchmark relevant options:
===========================
* --optimized-kernel-enable
Self-test hash parsing error: Token encoding exception
Started: Wed Oct 30 11:11:22 2019
Stopped: Wed Oct 30 11:11:22 2019
Would someone to help me ?Tell me what's wrong with this?
Thanks a lot!
AND my system is Ubuntu 18.04,AMD Vega 56 :
Quote:john@ubuntu:~/crack$ ./hashcat-5.1.0-beta/hashcat.bin -I
hashcat (v5.1.0-1403-g87022919) starting...
OpenCL Info:
============
OpenCL Platform ID #1
Vendor..: Advanced Micro Devices, Inc.
Name....: AMD Accelerated Parallel Processing
Version.: OpenCL 2.1 AMD-APP (2982.0)
Backend Device ID #1
Type...........: GPU
Vendor.ID......: 1
Vendor.........: Advanced Micro Devices, Inc.
Name...........: gfx900
Version........: OpenCL 2.0
Processor(s)...: 56
Clock..........: 1590
Memory.........: 6949/8176 MB allocatable
OpenCL.Version.: OpenCL C 2.0
Driver.Version.: 2982.0 (HSA1.1,LC)
RE: m13600 error,Self-test hash parsing error: Token encoding exception - philsmd - 10-30-2019
do you think this is the same problem https://github.com/hashcat/hashcat/issues/2200 ?
RE: m13600 error,Self-test hash parsing error: Token encoding exception - sdwzzx - 10-30-2019
(10-30-2019, 10:24 AM)philsmd Wrote: do you think this is the same problem https://github.com/hashcat/hashcat/issues/2200 ?
maybe is the same problem,but i'm not sure
RE: m13600 error,Self-test hash parsing error: Token encoding exception - philsmd - 10-30-2019
well, that was more like a rhetorical question !
we know that it has to do with hexadecimal fields and this recent commit (which in fact isn't wrong, but only brought the problem to light because it finally makes a correct test of TOKEN_ATTR_VERIFY_DIGIT) https://github.com/hashcat/hashcat/commit/b19761081148f0d6d57fad2eafefc7021285b1bb#diff-379173f28f1caa2d2d7cca759fbed3c3R1095-R1098
the 13600 = winzip format uses hexadecimals at some places in the format and we would need to fix the module (src/modules/module_13600.c) with TOKEN_ATTR_VERIFY_HEX instead of the digit test
RE: m13600 error,Self-test hash parsing error: Token encoding exception - sdwzzx - 10-31-2019
(10-30-2019, 04:49 PM)philsmd Wrote: well, that was more like a rhetorical question !OK,thanks for your hard working!
we know that it has to do with hexadecimal fields and this recent commit (which in fact isn't wrong, but only brought the problem to light because it finally makes a correct test of TOKEN_ATTR_VERIFY_DIGIT) https://github.com/hashcat/hashcat/commit/b19761081148f0d6d57fad2eafefc7021285b1bb#diff-379173f28f1caa2d2d7cca759fbed3c3R1095-R1098
the 13600 = winzip format uses hexadecimals at some places in the format and we would need to fix the module (src/modules/module_13600.c) with TOKEN_ATTR_VERIFY_HEX instead of the digit test