[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANO7a6y+nPvvu0ntL5fjgjuPTM0Xx1EWty7b7mOFHA2T6MxFGQ@mail.gmail.com>
Date: Mon, 9 Jul 2012 18:54:56 +0530
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Re: [john-users] Cracking Word files?
On Mon, Jul 9, 2012 at 6:00 PM, Rich Rumble <richrumble@...il.com> wrote:
> On Mon, Jul 9, 2012 at 8:13 AM, Elijah [W&P] <smarteam.support@...il.com> wrote:
>> Is there such a need to store path to a .doc file in a file with a task for
>> john? We are not storing the full filename where the hash comes from for
>> other formats so why to make such an exclusion which brings such
>> inconsistency issues?
To solve the problem, in office2john either,
1. We can store only the basename of the file OR
2. We can encode colons into something.
Patches are welcome.
> I assume in office it
> would be necessary as well since the files in docx/xlsx etc are in a
> compressed archive (maybe OLE container) and once the candidate
> hash/pass is found it has to check to see if that's the right one? I
> can't follow the source well so that may not be true for either :)
In office format, we don't need the path for cracking. The path is
there for user usage only.
--
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.
