Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 08 Oct 2014 10:01:21 +0300
From: Shinnok <>
Subject: Re: Johnny GUI current state

On 10/6/2014 6:30 PM, Aleksey Cherepanov wrote:
> Hi Shinnok,
> On Mon, Oct 06, 2014 at 01:29:47PM +0300, Shinnok wrote:
>> On 10/3/2014 8:15 PM, Aleksey Cherepanov wrote:
>>> Hi Shinnok,
>>> On Fri, Oct 03, 2014 at 04:27:48PM +0400, Aleksey Cherepanov wrote:
>>>> On Fri, Oct 03, 2014 at 02:02:39PM +0300, Shinnok wrote:
>>>>> Long time since I've been posting here or got in touch with either Solar or
>>>>> Aleksey, so I want to say Hi first.
>>>>> What's the current development state and future for the Johnny GUI. Has it
>>>>> been getting any love, planning or requests lately? I've skimmed the list a
>>>>> bit but I don't see much. Has there been any GSoC'ers assigned to it lately?
>>>> I am responsible for Johnny now. I spent 1 month on it during gsoc
>>>> 2012 and I should finish it. Though I did not touch it for a long
>>>> time (2 years?! oh... my bad).
>>>> I released version 1.1. I cleaned out unimplemented stubs. Also I
>>>> reworked "Options" page/tab. Only core john is supported.
>>> Johnny is far behind bash auto-completions made by Frank Dittrich. He
>>> was my mentor during the gsoc.
>>> Work together would be a lot of fun. Would you like to try? Propose a
>>> list of features for the next release and mark features that you'd
>>> like to try to implement yourself, please!
>>> Thanks!
>> Hey Aleksey,
>> Nice to hear from you.
>> Far behind auto-completions as in the features it integrates with JtR?
> Not sure about core john, auto-completions get lists from config file
> though 'hidden' option of john with jumbo (`john
> --list=hidden-options`). I think we could do similarly for drop-down
> lists in Johnny, similar support of that parsing john's config may be
> added later for core john.
>> You've guessed my intentions, I'll have some spare time in this last quarter
>> and I'd like to use some of it on something gratifying, like Johnny. Get it
>> a bit farther then it is now.
> Awesome! You're welcome!
>> Without further ado, let's get down to business, what's the current latest
>> branch that you've worked on(guessing master by the looks of it)?
> Yes, 'master' branch is the main. Though all branches should be the
> same now. I have wrong layout of branches so it may be reasonable to
> remove them all and make it different way.
>> I'll take
>> that current version for a spin and then come up with a plan that we can
>> both work on. I have some features of my own that I'd like Johnny to support
>> so I'll include those in that plan too. Any other standing features or plans
>> that Johnny might have accumulated throughout time could be best added to
>> this discussion.
> Great! I'll add to the list too.
> Thanks!
I've sent the plan as a separate e-mail. As for Github, I pulled your 
master on top of mine, thus you can go ahead and remove all the other 
branches you have after you've verified that master is indeed the latest.
I propose we work on master, with separate feature/refactoring branches 
as needed then merging back into master, for the sake of simplicity.
We can then tag releases from master too. How does this sound for you?


Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.