[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP2470976F590562174A58A07FD910@phx.gbl>
Date: Thu, 30 May 2013 09:26:58 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: 333 (half-badass number?)
On 05/30/2013 12:41 AM, magnum wrote:
> In bleeding, there is limited wildcard and class support since some time, for example:
>
> ../run/john -test -format:cpu
> ../run/john -t -form:gpu
> ../run/john -t -form:cuda
> ../run/john -t -form:opencl
Is there an easy way to test whether --format=cpu|gpu|opencl|cuda is
supported or not? (So that I can provide bash completion if it is
supported, but don't suggest completions that aren't supported?
Should I just check --list=build-info and enable it if the format
interface version is >= 11 and we have a jumbo version?
> ../run/john -t -form:dynamic
This should already work with bash completion, because I complete dy to
dynamic, then to dynamic_, and then list all the individual dynamic formats.
> ../run/john -t -form:hmac-*
> ../run/john -t -form:krb5*
Currently bash completion does this:
$ ./john --format=hmac-
hmac-md5 hmac-sha224 hmac-sha384
hmac-sha1 hmac-sha256 hmac-sha512
Should I add a hmac-* (of course, only if there already are multiple
possible completions)?
Should this also depend on jumbo + format version >= 11?
> We could add support for leading wildcard too, like -format:*sha256. I saw no need for it at the time.
--format=*256*
I think I'll not support that in bash completion, even if you decide to
add support for it.
Frank
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.
