[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOuOLUJvpW3pcDGkteYqD69EjVeajuL6ZN_mHJ5iuBYRvV=xSQ@mail.gmail.com>
Date: Mon, 25 Nov 2013 14:19:06 -0500
From: Zach Bevilacqua <bertwithcookie@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: OMP on windows hangs after about 2 hours
On Mon, Nov 25, 2013 at 2:04 PM, magnum <john.magnum@...hmail.com> wrote:
> On 2013-11-25 17:55, Zach Bevilacqua wrote:
>
>> $ john --list=format-all-details --format=wpapsk | tail -2 | awk '{print
>> $3}' > testhash
>> $ john testhash -inc:lower -progress=1800
>>
>> Kept running with no issue. The original cracking function seemed to be
>> hung with high CPU, eventually I killed the process via the task manager.
>> Upon --restore the timer showed the cracking time to have been running the
>> whole time, I don't know if the cracking was actually running still or
>> just
>> the timer.
>>
>
> If the cracking would somehow stall and the timer still run, your c/s
> figures would decrease for each status update. What speed was/is shown
> after resuming?
>
> I'm not sure what to make out of this. Maybe it's a mingw64 problem. The
> md5crypt format is among our best tested but the win64 build target is
> bleeding-edge. I have no way to test the latter at all. Maybe just for
> testing you could try resume or restart an md5crypt session with
> OMP_NUM_THREADS=1 and see if it survives longer.
I'll try with one thread see if I get a better result. I figured there
would have been no issues with the format. Would there be any issue with
AMD vs Intel or the type of video card? Heat isn't an issue, never reached
above 45c...
>
>
> magnum
>
> NVM I restored the wrong one.... My fault. The original one actually froze
completely.
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.
