Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D736264.3000108@bredband.net>
Date: Sun, 06 Mar 2011 11:31:00 +0100
From: magnum <rawsmooth@...dband.net>
To: john-dev@...ts.openwall.com
Subject: Re: md5_gen, proposed functionality

On 03/06/2011 05:18 AM, jfoug wrote:
>
>
>> -----Original Message-----
>> From: magnum [mailto:rawsmooth@...dband.net]
>> On 03/05/2011 03:36 AM, JimF wrote:
>>> Explain a little more the situations you have need for this.
>>>
>>> 1. Is it input file password hashes?
>>
>> The situation is EXACTLY like NT hashes: The input file is ASCII, but
>> the hashes *was created from* plaintexts encoded in UTF16.
>>
>> Consider this:
> ...snip...
>>> 4. Exactly what do you 'think' needs done?
>>
>> On a higher level and not caring about performance, I would like to be
>> able to create a md5_gen(1xxx) or a thin format that uses unicode($p)
>> instead of just ($p).
>>
>> We have functions like MD5GenBaseFunc__append_salt so maybe we can have
>> a function like MD5GenBaseFunc__convert2unicode.
>>
>> Then I could state md5(unicode($p)) like this:
>>
>> [List.Generic:md5_gen(1100)]
>> # expression shown will be the string:   md5_gen(1100) md5(unicode($p))
>> Expression=md5(unicode($p))
>> Func=MD5GenBaseFunc__InitialLoadKeysToInput
>> Func=MD5GenBaseFunc__convert2unicode
>> Func=MD5GenBaseFunc__crypt
>> Test=md5_gen(1100)16c47151c18ac087cd12b3a70746c790:test1
>> Test=md5_gen(1100)537e738b1ac5551f65106368dc301ece:thatsworking
>> Test=md5_gen(1100)849ee1b88b5d887bdb058180a666b450:test3
>
>
> Unfortunately, there are not easy, one size fits all 'ways' to do the
> convert.  There would have to be a whole LOT of converts.  I would much
> rather do something like this:
>
> Expression=md5(unicode($p))
> Func=MD5GenBaseFunc__clean_input
> Func=MD5GenBaseFunc__setmode_ascii_to_unicode
> Func=MD5GenBaseFunc__append_keys
> Func=MD5GenBaseFunc__crypt
>
> For
> Expression=md5(unicode($p.$s))
> Func=MD5GenBaseFunc__clean_input
> Func=MD5GenBaseFunc__setmode_ascii_to_unicode
> Func=MD5GenBaseFunc__append_keys
> Func=MD5GenBaseFunc__append_salt
> Func=MD5GenBaseFunc__crypt
>
> For
> Expression=md5(unicode($p).$s))
> Func=MD5GenBaseFunc__clean_input
> Func=MD5GenBaseFunc__setmode_ascii_to_unicode
> Func=MD5GenBaseFunc__append_keys
> Func=MD5 GenBaseFunc__setmode_normal
> Func=MD5GenBaseFunc__append_salt
> Func=MD5GenBaseFunc__crypt
>
> NOTE, there are many sets, of keys, inputs, salts, etc.  I would hate to
> have to double them. Also, each of them have 2 (or even 3) 'separate'
> sections within each of these.  However, setting data movement 'states'
> makes it pretty easy to flip back and forth between data conversion 'modes'.
>
>
> Jim
>

That makes sense and I think it would cover all situations.

magnum

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.