Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 29 May 2015 15:22:55 +0200
From: Frank Dittrich <>
Subject: Re: Signal handling within john formats.

On 05/29/2015 03:10 PM, Sayantan Datta wrote:
> This is a part of my experiment/learning exercise/tinkering scheme and
> it may or may not make its way into jumbo. The problem is, I'm using a
> randomized algorithm and sometimes it is profitable(performance wise) to
> bail out and restart the algorithm with new set of parameters. When I
> see there is not enough progress within a stipulated amount of time, I'd
> like to bail out and restart. This is why I need alarm()/setitimer(). I
> need to run the algorithm within fmt->restart() and within
> fmt->crypt_all() once in a while(i.e after some hashes are cracked).

Why do you need to implement this inside john, instead of implementing
another program which controls john, kills running sessions when they
become ineffective, and start new, possibly more effective sessions?


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.