[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160207235413.GA4953@openwall.com>
Date: Mon, 8 Feb 2016 02:54:14 +0300
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: Cracking luks volume
Thank you for helping provide user support, Rich!
On Sun, Feb 07, 2016 at 12:21:11PM -0500, Rich Rumble wrote:
> You can use the KnownForce (external mode), rules, prince (plus
> rules), or mask mode.
KnownForce is pretty much obsoleted by mask. In jumbo, it currently
serves more as an external mode example than as something to use.
> Mask: (I don't know how to escape star, semi-colon, colon, gt/lt,
> question mark...)
> -mask=F6TgW8D8[!@...^]F6TgW8D8[+={}.,-]F6TgW8D8?s
To include characters that are special for the shell, quoting specific
to the shell one is using should be used. With most Unix shells, you'd
put the string in single quotes, like this:
-mask='F6TgW8D8[!@...^*;:<>]F6TgW8D8[+={}.,-]F6TgW8D8?s'
Question mark is also special to mask mode itself, but only when it's
not inside square brackets. To specify a literal question mark when not
inside square brackets, you need to double it. For example:
$ ./john --mask='[12]??[34]' --stdout
1?3
2?3
1?4
2?4
4p 0:00:00:00 100.00% (2016-02-08 02:48) 25.00p/s 2?4
but:
$ ./john --mask='[a?b]' --stdout
a
?
b
magnum, Sayantan -
However, this appears buggy:
$ ./john --mask='[1?9]' --stdout
1
[
]
3p 0:00:00:00 100.00% (2016-02-08 02:50) 50.00p/s ]
and e.g. '[1?2]' is even worse. Looks like we're (wrongly) expanding
?digit (but not ?letter) even inside square brackets? This looks like a
jumbo bug to me.
Alexander
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.
