[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+E3k91_RoEQiXXbvXfp9jhNm3eHfbnRAVH2T0TNgiFTPpgViA@mail.gmail.com>
Date: Sat, 11 Oct 2014 18:17:42 -0800
From: Royce Williams <royce@...ho.org>
To: john-users@...ts.openwall.com
Subject: Re: thanks for GPU temp and fan speed in status line
On Sat, Oct 11, 2014 at 6:02 PM, magnum <john.magnum@...hmail.com> wrote:
> On 2014-10-12 03:21, Royce Williams wrote:
>>
>> On Sat, Oct 11, 2014 at 4:37 PM, magnum <john.magnum@...hmail.com> wrote:
>>>
>>> This bug only affected --list though, not status lines. Just for peace of
>>> mind, could you run a brief crack against some test hash using a CUDA
>>> format
>>> and double-check that it prints the correct temp/fan values in the status
>>> line too?
>>
>>
>> I can't verify this at this time because I can't seem to get john to
>> produce a status line on this run. This happens to me once in a while
>> on a variety of platforms, but I've never really understood why (may
>> be a FAQ item, but I couldn't find it when I last checked).
>>
>> $ ./john --format=phpass-cuda test.phpass
>> Loaded 1 password hash (phpass-cuda [MD5 CUDA])
>> Press 'q' or Ctrl-C to abort, almost any other key for status
>>
>>
>> [this whitespace is me pressing "enter" to no effect,
>> even after waiting a few minutes]
>>
>>
>> Session aborted
>
>
> This is usually because you have lots of salts loaded and a slow format
> (you'd only get a reaction once all salts are processed) but in this case
> there's only one salt so I'm not sure what happens.
Me, neither. As it crops up I'll try to determine what the
symptomatic sessions have in common.
> I just tried this:
>
> $ ./john -form:phpass --list=format-tests | cut -f3 > phpass.in
> $ ./john -form:phpass-cuda phpass.in -progress-every=1
[snip]
That really teaches me to fish! Looks good here.
$ ./john -form:phpass --list=format-tests | cut -f3 > phpass.in
$ ./john -form:phpass-cuda phpass.in -progress-every=1
Loaded 16 password hashes with 14 different salts (phpass-cuda [MD5 CUDA])
Press 'q' or Ctrl-C to abort, almost any other key for status
test2 (?)
test3 (?)
2g 0:00:00:00 20.20% 2/3 (ETA: 18:13:11) 2.739g/s 0p/s 132558c/s
220931C/s GPU:75°C fan:50% 123456..scotty!
test1 (?)
123456 (?)
123456 (?)
123456 (?)
test1 (?)
test4 (?)
8g 0:00:00:01 38.55% 2/3 (ETA: 18:13:14) 4.278g/s 17249p/s 293236c/s
327734C/s GPU:75°C fan:50% scouts!..thelorax?
(...)
Forcing the specific device ID gives the expected results as well (0
is the cool card, 1 is the hot card)
$ john --device=0 -form:phpass-cuda phpass.in -progress-every=1
Loaded 16 password hashes with 14 different salts (phpass-cuda [MD5 CUDA])
Remaining 8 password hashes with 8 different salts
Press 'q' or Ctrl-C to abort, almost any other key for status
0g 0:00:00:00 20.20% 2/3 (ETA: 18:15:07) 0g/s 0p/s 129024c/s 129024C/s
GPU:34°C fan:32% 123456..scotty!
0g 0:00:00:02 62.25% 2/3 (ETA: 18:15:10) 0g/s 32095p/s 288859c/s
288859C/s GPU:35°C fan:32% tika?..Nikita9
0g 0:00:00:02 80.60% 2/3 (ETA: 18:15:09) 0g/s 35576p/s 332047c/s
332047C/s GPU:35°C fan:32% Nikki9..7politics
Session aborted
$ ./john --device=1 -form:phpass-cuda phpass.in -progress-every=1
Loaded 16 password hashes with 14 different salts (phpass-cuda [MD5 CUDA])
Remaining 8 password hashes with 8 different salts
Press 'q' or Ctrl-C to abort, almost any other key for status
0g 0:00:00:00 20.20% 2/3 (ETA: 18:15:14) 0g/s 0p/s 140243c/s 140243C/s
GPU:77°C fan:52% 123456..scotty!
0g 0:00:00:01 62.25% 2/3 (ETA: 18:15:15) 0g/s 36242p/s 326184c/s
326184C/s GPU:78°C fan:54% tika?..Nikita9
Session aborted
Royce
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.
