Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 20 Aug 2015 06:12:16 -0400
From: Mathieu Laprise <>
Subject: Re: Johnny v2.1 and beyond

Take a look at m'y branche, I manage to make some generic data structures
yesterday that could allows us to add a new script in 2 lines without
writing UI code or if else if. It could have any number of checkable(like
is json?) or file or text paramètres.

On Thu, Aug 20, 2015 at 4:03 AM, Shinnok <> wrote:

> On Aug 19, 2015, at 7:45 PM, Mathieu Laprise <>
> wrote:
> On Tue, Aug 18, 2015 at 10:30 AM, Mathieu Laprise <>
> wrote:
>> 2) Do we hardcode the format based on the latest jumbo or ... ?
> The *2john support task is longer than we thought. We can't just prompt a
> dialog to select the file and run the script on it. Some scripts takes 1
> parameter, others 2 and some even require options like -i --json etc..
> Do a generic UI that won't adapt and put all generic fields like input
> file 1, input 2, parameter 1(only generic words, no case by case) have
> advantages over the command line script which show USAGE for each ?
> As I see it, a nice UI would do :
> User checks unshadow :
> DATABASE-FILE : LineEdit + Browse button
> CELL-NAME LineEdit only
> ---------
> User checks Mozilla, previous files disappear and this appears :
> key3.db file(s) : LineEdit + Browse button
> ----------
> User check LastPass
> Email adress : LineEdit
> LastPass *._lpall.slps file : LineEdit + Browse button
> We have like 60 2*john scripts with a lot of case by case to do if we want
> to have something polished that will compete against command line usage and
> help not-experience user. That seems hard to do in the left time. Do we
> need an intuitive UI like that or do you have something more generic in
> mind that would be better than command line usage ? You can see my current
> UI in my branch.
> Yes, this hard to do, given that the scripts don't follow a certain
> format/style. We'll end up with a half-assed solution that would be even
> harder to work with than the actual shell invocation itself. Let's abandon
> this task for now(I'll take a look at what you have in your branch later)
> and substitute with task 2.4.2:
> • Add tooltips to all UI actions that are not very self explanatory to a
> new comer
> Do a sweep of the UI. Basically, every action, button, checkbox and
> line-edit should have a tooltip set.
> Shinnok

Content of type "text/html" skipped

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.