[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d4583667300514d4910a20cc1acdc9ae@smtp.hushmail.com>
Date: Mon, 10 Mar 2014 01:17:22 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Pause/abort from filesystem stimuli
On 2014-02-23 12:29, magnum wrote:
> Off-list, on 2014-02-23 10:38, magnum wrote:
>> On 2014-02-22 22:14, Solar Designer wrote:
>>> Maybe we need to add a feature to JtR where it could be paused by
>>> another
>>> user on the system (when that feature is enabled in the config) - e.g.,
>>> maybe it could check for /var/run/john/pause every few seconds, and we'd
>>> add users permitted to use this feature to a group with write access to
>>> /var/run/john. Maybe it should honor the /var/run/john/pause file only
>>> as long as its timestamp is recent (so that if someone forgets to remove
>>> the pause file, john would eventually resume cracking).
>>
>> That might be a good idea. Maybe also /var/run/john/abort to gracefully
>> stop a job.
This is now implemented and default filenames are the ones mentioned -
but they can be reconfigured in john.conf (or disabled, if coemmented out).
> A really KISS patch would check those files right after session-save,
> not introducing any more timers and with ignorable overhead. But that
> could mean a very long reaction time (though normally within 10 minutes).
I opted to poll the files every three seconds. Before going to sleep, a
status line is emitted and session is saved. When resuming, times are
reset so pause time is disregarded.
magnum
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.
