[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <F9E57B25-F3BC-4040-9E14-EB02AFAE3910@shinnok.com>
Date: Mon, 3 Aug 2015 15:25:52 +0300
From: Shinnok <admin@...nnok.com>
To: john-dev@...ts.openwall.com
Subject: Re: Johnny: core/jumbo differences
> On Jul 31, 2015, at 11:40 PM, Frank Dittrich <frank.dittrich@...lbox.org> wrote:
>
> On 07/31/2015 10:17 PM, Mathieu Laprise wrote:
>> Thanks Frank for the documentation, I'll look at those files. If I take
>> prince for example, I see that there are a lot of options in the github
>> issue doc. Do john-devs want Johnny to put all available options in the
>> UI for those 3 modes even if it has risk of confusing less advanced user
>> or we could choose the most important ? We could do it 3 ways:
>> 1) Only add the options relevant to the majority of the users.
>> 2) Add all options in johnny. However, we could separate in two areas
>> (essential options for the mode vs advanced options) (differentiate
>> optional vs essential parameters)
>> 3)Add all options and don't separate them.
>
> I don't really know what users of johnny expect.
> But I think most users who would prefer johnny over john on the command
> line are best served with hiding much of the complexity.
>
I'm not sure hiding is the best approach, unless they're some really obscure options not expected to be used in 90% of the cases. We should expose as much as we can in favor of JtR feature completeness and strive to help the user decide if a certain option is good for him or not and where to get more info in regards to it.
Shinnok
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.
