Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 21 Sep 2015 18:45:14 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: hashcat rules (in)compatibility (was: Judy array)

On Mon, Sep 21, 2015 at 06:17:09PM +0300, Solar Designer wrote:
> Now we might want to introduce a new command character to do what
> hashcat's 'x' does.  What do we call it?  'h' or 'H' for hashcat?  And
> what would the other mean, then?  (It's good to use lower/uppercase
> command chars for something related or opposed.)  Maybe 'e' for erase
> (hashcat already defines 'E' for something else)?  Any better idea?

Another idea is to use 'm', for multi-character delete.  We already use
'M' for memorize current word.  Maybe it's better to reserve 'm' for
something memory-related, or something else where this letter would be
more essential.

> There are also compatibility issues with 'L', 'R' (different syntax and
> semantics: keyboard vs. bitwise shifts), '+' (we define it only for
> single crack mode, though), and '*' (vs. Crack's use of this command).

Alexander

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ