Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANO7a6wK8b5oSiddv52b7YrdmdAMv3NM02P8-Ltexme5gKDuYQ@mail.gmail.com>
Date: Sun, 2 Dec 2012 08:54:39 +0530
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Document Decryption:Fourth Year Project

On Sun, Dec 2, 2012 at 4:27 AM, magnum <john.magnum@...hmail.com> wrote:
> On 1 Dec, 2012, at 20:28 , shane Shane <shane@...twareontheside.info> wrote:
> I'm doing a fourth year project about cracking encrypted documents,
> MSOffice, OpenOffice and PDF files on a distributed network of raspberry pi
> micro computers. I'm using john as the cracking software on each of the
> slave nodes in the network. If there is anything that needs to be done to
> help speed up the cracking of these documents types or otherwise improve
> john's ability to crack documents please let me know. I'd love help out.
>
>
> Among shit we need done we do have an npdf2john that seriously needs work.
> Apart from that, be sure to tell us any real shortcomings. I'm not really
> updated on openoffice - what do we need to do to support cracking it it real
> fast?

Yes, npdf2john currently sucks. I am sure that ndpf2john can be done
under 300 lines of code (if one is able to figure out the logic of the
current Perl code).

Code for cracking OpenOffice documents (which use Blowfish encryption)
using GPU is already present.

However, new OpenCL code needs to be written for cracking OpenOffice
documents which use AES encryption. The current PBKDF2 OpenCL code
doesn't handle input hashed passwords of length 32 bytes (generated by
SHA256).

-- 
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.