[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABob6ir+qwXkUg6WpWV75POcAN9SEhBy1WERCErXWsYHXcKTdg@mail.gmail.com>
Date: Tue, 12 Mar 2013 22:38:49 +0100
From: Lukas Odzioba <lukas.odzioba@...il.com>
To: john-dev@...ts.openwall.com
Subject: *2john utils dev guide
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.
