Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 24 Jul 2015 17:59:35 +0300
From: Shinnok <admin@...nnok.com>
To: john-dev@...ts.openwall.com
Subject: Re: Mathieu's weekly report #12


> On Jul 21, 2015, at 1:52 PM, Shinnok <admin@...nnok.com> wrote:
> 
> 
>> On Jul 20, 2015, at 8:20 PM, Rich Rumble <richrumble@...il.com> wrote:
>> 
>> On Mon, Jul 20, 2015 at 12:36 PM, Shinnok <admin@...nnok.com> wrote:
>>> 
>>> On Jul 20, 2015, at 2:04 PM, Mathieu Laprise <mathlaprise@...il.com> wrote:
>>> 
>>> - Export tableview to CSV
>>> 
>>> 
>>> Is this useful to anyone else? What about other formats?
>>> 
>>> If not we can skip this one.
>> I'd like this if it's simple to code, CSV that is. I wouldn't have
>> interest in other formats (xml, json etc..)
> 
> It shouldn't be too difficult to write it manually. CSV is a simple format after all.
> 

What about colon separated text, exactly like a password file?

This could be useful in the following contexts:
1. User used several input files;
2. User used 2john formats;
3. A combination of both;

Having the ability to export to exactly john format could be useful right? Sort of like the undoing of 2john. This was part of my original task too, along with CSV.

Also what should we export? In my thinking everything, meaning cracked and uncracked passwords. Maybe we could abuse the newly added filter functionality to only export parts of the PASSWORD table, which will enable both of the previous and more, like exporting only cracked rows of type md5.

Shinnok

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ