[<prev] [next>] [day] [month] [year] [list]
Message-ID: <56DB5A32.6080707@gmail.com>
Date: Sat, 5 Mar 2016 19:14:10 -0300
From: Claudio André <claudioandre.br@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: devices for --dev= option
W dniu 05.03.2016 o 18:45, Matus UHLAR - fantomas pisze:
> yes, but I somehow couldn't get --dev
You are probably doing something wrong. Below a few examples of valid
commands:
$ ../run/john -list=opencl-devices
[all devices info]
$ ../run/john -list=opencl-devices -dev=1
[only device 1 info]
> autoswitching formats to nvidia or opencl versions would be great...
Examples of real usages, even JtR auto-detecting based on real hashes
(and filtering only OpenCL formats).
$ ../run/john ~/data/test512_5.in -form=opencl -mask:?l?l?a?d?a?a?a
Device 6: GeForce GTX TITAN X
Warning: detected hash type "Raw-SHA512-ng-opencl", but the string is
also recognized as "Raw-SHA512-opencl"
Use the "--format=Raw-SHA512-opencl" option to force loading these as
that type instead
Using default input encoding: UTF-8
Loaded 3062025 password hashes with no different salts
(Raw-SHA512-ng-opencl [SHA512 OpenCL])
[...]
$ ../run/john -form=nt-opencl --test -dev=1
Device 1: Tahiti [AMD Radeon HD 7900 Series]
Benchmarking: nt-opencl, NT [MD4 OpenCL]...
DONE
Raw: 60817K c/s real, 76021K c/s virtual
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.
