|
Message-ID: <c7e4a2778a6e2812e915601a774a671f@smtp.hushmail.com> Date: Mon, 20 May 2013 09:47:31 +0200 From: magnum <john.magnum@...hmail.com> To: john-users@...ts.openwall.com Subject: Re: md5(md5$pass).$salt) On 19 May, 2013, at 18:05 , websiteaccess@...il.com wrote: > I'm not sure JTRid able to handle hash with long salt (see below) > > hash = af26237e6ff340a0c8176f754ab8d7a5 salt = > wxcbHtMBqv,Pv*6.=)B$B`AR8FpME@ > > I tried > > $dynamic_1007$af26237e6ff340a0c8176f754ab8d7a5 > wxcbHtMBqv,Pv*6.=)B$B`AR8FpME@ > $dynamic_1007$af26237e6ff340a0c8176f754ab8d7a5$wxcbHtMBqv,Pv*6.=)B$B`AR8FpME@ > $dynamic_1007$af26237e6ff340a0c8176f754ab8d7a5:wxcbHtMBqv,Pv*6.=)B$B`AR8FpME@ Dynamic 1007 is for a fixed salt length of 3. I think you need to write a new dynamic format in dynamic.conf. The below is untested but might work fine: [List.Generic:dynamic_1351] Expression=md5(md5($p).$s) (long salt) Flag=MGF_SALTED Flag=MGF_NOTSSE2Safe Flag=MGF_KEYS_BASE16_IN1 Func=DynamicFunc__set_input_len_32 Func=DynamicFunc__append_salt Func=DynamicFunc__crypt_md5 Test=$dynamic_1351$daa61d77e218e42060c2fa198ac1feaf$SXB:test1 BTW, the salt separator is '$' and -field-separator-char does not change that. If some salts contain '$' I believe they'll have to be hex encoded. 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.