Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CANO7a6wwUxe-A+HQ2DrvJeRbxHMCnHHp8R4WCyV+sDbCDS_c3Q@mail.gmail.com>
Date: Thu, 5 Apr 2012 21:24:18 +0530
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: EPiServer hashes

On Thu, Apr 5, 2012 at 3:01 PM, Dhiru Kholia <dhiru.kholia@...il.com> wrote:
> On Thu, Apr 5, 2012 at 2:09 PM, Per Thorsheim <per@...rsheim.net> wrote:
>> 2. I will make a bunch of other examples as well as find a decent way of exporting them (user:hash:salt or just hash:salt). I'm on vacation now, back to work and colleagues with episerver on Tuesday. I'll get back to you then.
>
> Sure. (user:hash:salt) seems to be fine. I can write a small utility
> to convert (user:hash:salt) into format required by JtR (namely
> "user:$episerver$*salt*hash"). Thanks!

I have added support to crack new EPiServer hashes to JtR
(https://github.com/magnumripper/magnum-jumbo). So far, the code is
not tested much (might crash or not work!). The patch has OMP support
too.

The input format is
"user:$episerver$*version*base64(salt)*base64(hash)" where version ==
0 for now.
E.g. testUser:$episerver$*0*fGJ2wn/5WlzqQoDeCA2kXA==*UQgnz/vPWap9UeD8Dhaw3h/fgFA=

--
Cheers,
Dhiru

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.