Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 29 Dec 2011 16:34:33 -0500
From: Jordan Bradley <jordan.w.bradley@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Making a thread safe implementation of bitslice DES

On Thu, Dec 29, 2011 at 4:27 PM, Solar Designer <solar@...nwall.com> wrote:
> On Thu, Dec 29, 2011 at 04:20:37PM -0500, Jordan Bradley wrote:
>> On Thu, Dec 29, 2011 at 4:12 PM, Solar Designer <solar@...nwall.com> wrote:
>> >
>> > What character encoding would you want to use on input to JtR, such as
>> > in wordlists?
>>
>> Considering that with 2chan style tripcodes, the unicode input is
>> converted to shift-jis, using anything other than SJIS is pointless as
>> far as tripcodes are concerned.
>
> I asked about input to JtR.  If you're fine with having the input right
> in the encoding needed for tripcodes, then I don't know what we're even
> discussing now - there's no issue as-is.

Sorry I misunderstood. In that case I suppose Unicode would be the
most practical because all the other character maps are contained in
it as far as I know. The input would have to be converted to their
proper encoding, for example: shift-jis for tripcodes.

>
> Well, I think we may need to implement a Shift-JIS aware alternative to
> incremental mode, maybe as an external mode or maybe built-in - because
> not everything is reasonably crackable with a wordlist.
>

That's more or less what I've been trying to write myself.

-- 
Jordan Bradley

Powered by blists - more mailing lists

Your e-mail address:

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