|
Message-ID: <003b01d3a13c$59d0eb50$0d72c1f0$@netscape.net> Date: Thu, 8 Feb 2018 19:24:29 -0500 From: <rs904c@...scape.net> To: <john-users@...ts.openwall.com> Subject: JtR 1.8.0.12-jumbo-1-bleeding-e6214ceab 2018-02-07 compiled for Windows, available on the wiki John Users, I've compiled John the Ripper1.8.0.12-jumbo-1-bleeding-e6214ceab 2018-02-07 for 64-bit windows and placed on the custom builds site at, http://openwall.info/wiki/john/custom-builds ************* Run-Time Errors during Testing *********************** The built-in test results died at Benchmarking: sha1crypt-opencl, (NetBSD) [PBKDF1-SHA1 OpenCL 4x] Information about this build: -Does not include vncpcap2john and SIPdump, since this does not easily compile on Windows. -This contains the MPI+OMP SSE4.2 build of John the Ripper for MS Windows 64-bit, compiled in MS Windows with the latest version of cygwin64. Your CPU must support the SSE4.1 instruction set in order to run these. -This includes the 12 cygwin DLLs need to run John. -Compiled with gcc version 6.4.0 The following test results are included: john-built-in-test-results.txt john-test-suite-test-results.txt ./john -list=build-info Version: 1.8.0.12-jumbo-1-bleeding-e6214ceab 2018-02-07 17:56:37 +0100 Build: cygwin 64-bit x86_64 SSE4.2 AC MPI + OMP SIMD: SSE4.1, interleaving: MD4:3 MD5:3 SHA1:1 SHA256:1 SHA512:1 CPU tests: SSE4.2 $JOHN is ./ Format interface version: 14 Max. number of reported tunable costs: 4 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: 6.4.0 OpenCL headers version: 2.2 Crypto library: OpenSSL OpenSSL library version: 0100020ef OpenSSL 1.0.2n 7 Dec 2017 GMP library version: 6.1.2 File locking: fcntl() fseek(): fseek ftell(): ftell fopen(): fopen memmem(): System's Compiled by: 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.