Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 01 Jun 2015 22:33:19 +0200
From: Marek Wrzosek <marek.wrzosek@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Bleeding jumbo now defaults to UTF-8

W dniu 01.06.2015 o 18:04, magnum pisze:
> On 2015-06-01 16:47, magnum wrote:
>> You can do a try-catch in Perl (actual command is 'eval' iirc).
>> Pseudo-code:
>>
>> For each UTF-8 line of input {
>>      skip any pure ASCII
>>      try encoding to CP1234
>>      if it worked, print it
>> }
>>
>> Unless you need this a lot you shouldn't create new files (they only add
>> a burden of maintenance). Just write this as a simple filter  where
>> actual encoding would be a command-line option, and feed it to john
>>
>> Example:
>> $ ./john -w:all.utf8.lst -rules:whatever hashfile
>> $ codepage.pl <all.utf8.lst -t cp1234 | ./john -pipe -enc:cp1234
>> -rules:whatever hashfile
>> $ codepage.pl <all.utf8.lst -t cp1235 | ./john -pipe -enc:cp1235
>> -rules:whatever hashfile
>> ...
>>
>> Let me see if I can whip up an actual implementation of that filter in
>> Perl. I'll be back.
> 
> Attached is a quick hack implementing this.
> 
> magnum
> 
WOW, that was fast! Thanks, magnum!
-- 
Marek Wrzosek
marek.wrzosek@...il.com

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.