[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHt5c3Y4gbAwvSxBTnmPbhq1hCynG9v+B_u4iE=sJGYDmpeMFA@mail.gmail.com>
Date: Mon, 06 Jan 2020 17:00:36 -0500
From: robertde12e <robertde12e@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: opencl not finds the password. In CPU it founds.
You want to know what I was told when I reported the same problem with wpapsk?Use Windows and to stop looking for bugs.Same exact problem in Windows too.I guess if you pretend the problem isn't there and don't look at it then it's ok, so stop looking for bugs use Windows it's your fault.I reality your not alone I had the same problem, solution there is none they don't care, or do what I did move to social engineering, you can get a hundred times the work done in the time it takes John to get one password.On Sun, Jan 5, 2020 at 8:07 PM Ricardo CYRYLZ MIESZKO <cyrylz.mieszko@...il.com> wrote:Hi.
When I use john with wordlist and --format=dmg-opencl or
--format=7z-opencl it can't find the password. If I use without the opencl
it finds.
I noted that error and I can't find a solution fot that: "Error creating
binary cache file: No such file or directory"
Much probably the binary creation error is the problem. How to solve it ?
I can't even find this error message in the John sources. That's weird. It
comes from some dependency maybe ?
I'm running on macOS Catalina, but the problem occurs in older macOS too.
Here is the opencl version:
0:00:00:00 - Building kernel and caching binary
0:00:00:00 - OpenCL LWS: 64, GWS: 8192 (both auto-tuned) (128 blocks)
0:00:00:00 - Hash type: 7z-opencl, 7-Zip (min-len 0, max-len 23)
0:00:00:00 - Algorithm: SHA256 AES OpenCL
0:00:00:00 - Will reject candidates longer than 69 bytes
0:00:00:00 - Candidate passwords will be buffered and tried in chunks of
8192
0:00:00:00 Proceeding with wordlist mode
0:00:00:00 - Wordlist file: dic.lst
0:00:00:00 - memory mapping wordlist (1353024 bytes)
0:00:00:00 - No word mangling rules
Device 3: AMD Radeon Pro 560X Compute Engine
Using default input encoding: UTF-8
Loaded 1 password hash (7z-opencl, 7-Zip [SHA256 AES OpenCL])
Cost 1 (iteration count) is 524288 for all loaded hashes
Cost 2 (padding size) is 7 for all loaded hashes
Cost 3 (compression type) is 1 for all loaded hashes
Error creating binary cache file: No such file or directory
Press 'q' or Ctrl-C to abort, almost any other key for status
0:00:00:00 Starting a new session
0:00:00:00 Loaded a total of 1 password hash
0:00:00:00 Cost 1 (iteration count) is 524288 for all loaded hashes
0:00:00:00 Cost 2 (padding size) is 7 for all loaded hashes
0:00:00:00 Cost 3 (compression type) is 1 for all loaded hashes
0:00:00:00 Command line: john --format=7z-opencl --pot=passwd.pot
--session=dic --wordlist=dic.lst hash.sec
0:00:00:00 - UTF-8 input encoding enabled
0:00:00:00 - Passwords will be stored UTF-8 encoded in .pot file
0:00:00:00 Device 3: AMD Radeon Pro 560X Compute Engine
0:00:00:00 - Building kernel and caching binary
0:00:00:00 - OpenCL LWS: 64, GWS: 8192 (both auto-tuned) (128 blocks)
0:00:00:00 - Hash type: 7z-opencl, 7-Zip (min-len 0, max-len 23)
0:00:00:00 - Algorithm: SHA256 AES OpenCL
0:00:00:00 - Will reject candidates longer than 69 bytes
0:00:00:00 - Candidate passwords will be buffered and tried in chunks of
8192
0:00:00:00 Proceeding with wordlist mode
0:00:00:00 - Wordlist file: dic.lst
0:00:00:00 - memory mapping wordlist (1353024 bytes)
0:00:00:00 - No word mangling rules
Warning: Only 5696 candidates left, minimum 8192 needed for performance.
0:00:00:00 - No stacked rules
0g 0:00:01:11 DONE (2020-01-05 15:51) 0g/s 652.8p/s 652.8c/s 652.8C/s
[xxxxxxx REMOVED]
Session completed
---------------------
==> Passwords Found ?
---------------------
0 password hashes cracked, 1 left
----------------------
Here is without opencl:
0:00:00:00 - Configured to use otherwise idle processor cycles only
0:00:00:00 - Will reject candidates longer than 84 bytes
0:00:00:00 - Candidate passwords will be buffered and tried in chunks of 4
0:00:00:00 Proceeding with wordlist mode
0:00:00:00 - Wordlist file: dic.lst
0:00:00:00 - memory mapping wordlist (1353024 bytes)
0:00:00:00 - No word mangling rules
0:00:00:00 - No stacked rules
0:00:06:02 + Cracked x.7z
0:00:06:02 Session completed
Using default input encoding: UTF-8
Loaded 1 password hash (7z, 7-Zip [SHA256 128/128 SSE4.1 4x AES])
Cost 1 (iteration count) is 524288 for all loaded hashes
Cost 2 (padding size) is 7 for all loaded hashes
Cost 3 (compression type) is 1 for all loaded hashes
Press 'q' or Ctrl-C to abort, almost any other key for status
0:00:00:00 Starting a new session
0:00:00:00 Loaded a total of 1 password hash
0:00:00:00 Cost 1 (iteration count) is 524288 for all loaded hashes
0:00:00:00 Cost 2 (padding size) is 7 for all loaded hashes
0:00:00:00 Cost 3 (compression type) is 1 for all loaded hashes
0:00:00:00 Command line: john --format=7z --pot=passwd.pot --session=dic
--wordlist=dic.lst hash.sec
0:00:00:00 - UTF-8 input encoding enabled
0:00:00:00 - Passwords will be stored UTF-8 encoded in .pot file
0:00:00:00 - Hash type: 7z, 7-Zip (min-len 0, max-len 28)
0:00:00:00 - Algorithm: SHA256 128/128 SSE4.1 4x AES
0:00:00:00 - Configured to use otherwise idle processor cycles only
0:00:00:00 - Will reject candidates longer than 84 bytes
0:00:00:00 - Candidate passwords will be buffered and tried in chunks of 4
0:00:00:00 Proceeding with wordlist mode
0:00:00:00 - Wordlist file: dic.lst
0:00:00:00 - memory mapping wordlist (1353024 bytes)
0:00:00:00 - No word mangling rules
0:00:00:00 - No stacked rules
[****REMOVED] (x.7z)
1g 0:00:05:56 DONE (2020-01-05 17:01) 0.002804g/s 8.481p/s 8.481c/s
8.481C/s [****REMOVED]
Use the "--show" option to display all of the cracked passwords reliably
Session completed
---------------------
==> Passwords Found ?
---------------------
x.7z:**************** [passwd removed]
----------------------
1 password hash cracked, 0 left
----------------------
Regards.
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.
