[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+TsHUCuqKPAoVVBpBqPuPyM0NRsz2M4OSoBkmQG1CZ3CR9eRQ@mail.gmail.com>
Date: Mon, 5 Aug 2013 15:23:55 +0530
From: Sayantan Datta <std2048@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Sayantan's Weekly Report #7
Hi Lukas,
On Sun, Aug 4, 2013 at 11:39 PM, Lukas Odzioba <lukas.odzioba@...il.com>wrote:
> It was in your repo, but I can't repoduce it now.
>
Did anything got cracked while you were running? There are certain
situations(very rare) in which you might get segfault at the end of
session. For example if something get cracked in the the last chunk of
password there is a possibility of segfault. The problem is that I can't
distinguish when a call to get_key() is meant for status checking and when
it is meant to get an actual cracked password.
> Another thing is that I have 2 gpus installed and when I run this
> format with mask mode on any of them my monitor is freeze till the end
> of cracking session, do you see similar behaviour?
> Still cant use this format with other modes (No given mask.Exiting...)
>
I haven't tested them on two GPUs but monitor freeze could happen when a
large number of hashes are loaded resulting in extremely long kernel run
time. But still, when only one out of two GPUs is used, the monitor
connected to idle GPU shouldn't get frozen.
I will add other modes this week.
Regards,
Sayantan
Content of type "text/html" skipped
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.
