Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 30 May 2013 10:51:39 +0200
From: magnum <>
Subject: Re: bash completion for format classes/wildcards (was: 333)

On 30 May, 2013, at 10:41 , Frank Dittrich <> wrote:
> On 05/30/2013 10:23 AM, magnum wrote:
>> On 30 May, 2013, at 9:26 , Frank Dittrich <> wrote:
>>> 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?
>> Actually it also works in unstable.
> As long as there is just one feature (supports format classes and
> generic format names) mapped to that variable, it might look a bit silly:
> Supported features: 00000001
> But that will certainly change over time.

How about re-listing --format with --list=hidden-options, like this:

$ ../run/john --list=hidden-options 
--format=CLASS            cpu, gpu, cuda, opencl, dynamic
--subformat=FORMAT        pick a benchmark format for --format=crypt

The printed list would reflect what's actually usable for this build.


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.