[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <061901d22f01$bd50d630$37f28290$@net>
Date: Tue, 25 Oct 2016 16:52:45 -0400
From: "Robert Harris" <rs904c@...scape.net>
To: <john-users@...ts.openwall.com>
Subject: JtR -test error 2016-10-25 in Cygwin x64
John Users,
I built John in Cygwin x64 bit and received an error during the built-in
test.
Someone up for fixing this?
Near the error in the built-in test:
Benchmarking: plaintext, $0$ [n/a]... DONE
Raw: 66236K c/s real, 66172K c/s virtual
Benchmarking: has-160 [HAS-160 32/64]... DONE
Raw: 4009K c/s real, 4013K c/s virtual
Benchmarking: sha1crypt-opencl, (NetBSD) [PBKDF1-SHA1 OpenCL 4x]...
Options used: -I
"/cygdrive/u/JtR/JohnTheRipper-bleeding-jumbo-2016-10-16(compiled without
pcap support)/run/kernels" -cl-mad-enable -DDEVICE_INFO=64 -DSIZEOF_SIZE_T=8
-DDEV_VER_MAJOR=0 -DDEV_VER_MINOR=13 -D_OPENCL_COMPILER -DHASH_LOOPS=1024
-DOUTLEN=20 -DPLAINTEXT_LENGTH=64 -DV_WIDTH=4
$JOHN/kernels/pbkdf1_hmac_sha1_kernel.cl
Build log: Invalid build option: without
Error -43 building kernel $JOHN/kernels/pbkdf1_hmac_sha1_kernel.cl.
DEVICE_INFO=96
OpenCL CL_INVALID_BUILD_OPTIONS error in common-opencl.c:1096 -
clBuildProgram failed.
$ ./john --list=build-info
Version: 1.8.0.9-jumbo-1-bleeding
Build: cygwin 64-bit SSE4.1-ac OMP
SIMD: SSE4.1, interleaving: MD4:3 MD5:3 SHA1:1 SHA256:1 SHA512:1
$JOHN is ./
Format interface version: 14
Max. number of reported tunable costs: 3
Rec file version: REC4
Charset file version: CHR3
CHARSET_MIN: 1 (0x01)
CHARSET_MAX: 255 (0xff)
CHARSET_LENGTH: 24
SALT_HASH_SIZE: 1048576
Max. Markov mode level: 400
Max. Markov mode password length: 30
gcc version: 5.4.0
OpenCL headers version: 2.1
Crypto library: OpenSSL
OpenSSL library version: 0100020af
OpenSSL 1.0.2j 26 Sep 2016
GMP library version: 6.1.1
File locking: fcntl()
fseek(): fseek
ftell(): ftell
fopen(): fopen
memmem(): System's
-Robert B. Harris from VA
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.
