Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 31 Jul 2015 16:16:39 +0300
From: Shinnok <>
Subject: Re: *2john conversion support

> On Jul 15, 2015, at 6:12 PM, Albert Veli <> wrote:
> I don't think it is necessary to convert the scripts. Either execute the script themselves and hope they have a #!/usr/bin/env python or similar shebang line. Or execute perl (with script as first argument) for .pl scripts and python (with script as first argument) for .py scripts. That will work in both windows and all unix dialects. And then fix the scripts as magnum suggested above so they all follow the same paradigm.
> On Wed, Jul 15, 2015 at 11:53 AM, Shinnok < <>> wrote:
> > On Jul 13, 2015, at 5:20 PM, Dhiru Kholia < <>> wrote:
> >
> > On Mon, Jul 13, 2015 at 11:37 AM, Shinnok < <>> wrote:
> >> The biggest issues stopping us from doing more than what I proposed are:
> >> 1. The tools are written in different languages
> >> 2. They don't follow an interface for either parameters, input nor output(error reporting, etc..)
> >> 3. We don't have a maintainer for those and trying to make heads or tails of it will already take too much of mine and Mathieu's time. We don't even know how many of them are still supposed to work, we don't have a file format/version to script mapping, etc..
> >>
> >> Maybe for another GSoC, we could have a potential task up for 2john script maintainer, to take care of converting them to a single scripting language, normalize to a single interface for parameters, input and output, test them and write some documentation. And after that work is done, Johnny could pick the results up and make more of it through an UI.
> >
> > I can probably pull this off in a weekend (or two).
> >
> > What is the expected output of this new unified single script (or
> > program)? Can it just print a bunch of hashes for a given input file?
> Misunderstanding here. I never mentioned a master script. What I was hinting at is a common unified interface that all scripts follow. Both arguments and stdin/stdout should follow the interface rules, Magnum's followup to this thread has a nice writeup on that. The other thing was that it's probably best to attempt to convert most scripts to a single language, agreed by all.

Windows is even more of a stretch. I'm not sure how much of an over-assumption would be for us to assume there is both perl and python installed and configured in the system path.

Does any of you incline towards using binaries done by Rich for inclusion in the redistributable? If they're self contained enough and working well that is, Rich?


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.