[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJaF1O3iSWL3Z8PNE1xG_Ma-aBWTBCiSOyrrP9kZp0qBcByOpw@mail.gmail.com>
Date: Tue, 12 Mar 2013 22:01:49 +0000
From: shane Shane <shane@...twareontheside.info>
To: john-dev@...ts.openwall.com
Subject: Re: *2john utils dev guide
I think it'd be a great idea, more consistent error messages would
certainly be more helpful to users. Not to mention some guides lines
on what languages are accepted/preferred would also be awesome.
Regards,
Shane
On Tue, Mar 12, 2013 at 9:38 PM, Lukas Odzioba <lukas.odzioba@...il.com> wrote:
>
> magnum,all,
>
> currently in jumbo we have plenty of tools like gpg2john, and our code
> will be growing up.
> Maybe it would be good idea to make short developer's guide according
> to utils (formats later?).
>
> It could be short list how code should behave, for example: support
> multiple input files, error handling, exit codes...
> I see at least two pros:
> -base of code consistency
> -clear guidelines for developers
>
> Please let me know what do you think,
>
> Lukas
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.
