[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <656f171f794b77e189cb2946f29fe05a@smtp.hushmail.com>
Date: Fri, 12 Dec 2014 11:33:04 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Crack 5.0's RULE_RESTART '*'
On 2014-12-12 04:12, Solar Designer wrote:
> We have a problem here: the same command character is used by *hashcat
> for a different purpose:
>
> https://hashcat.net/wiki/doku.php?id=rule_based_attack
>
> Swap @ N *XY Swaps character X with Y
>
> So we have to choose Crack compat vs. *hashcat compat.
>
> (We could also introduce some magic where '*' would act Crack-like if
> followed by a NOP and *hashcat-like otherwise, but I'd rather not do that.)
>
> *hashcat compat is of more practical relevance now, even though Crack
> was first to use this command character.
Hashcat also has +N and -N which I implemented but never committed
(http://www.openwall.com/lists/john-users/2013/09/22/10) because they
clash with Single mode concat, and rule reject.
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.
