[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANqzD4MRWYzaZWbY+P2dxqebhhkEcGv8rBRsuuxx0occ9WfSNg@mail.gmail.com>
Date: Mon, 9 Jul 2012 22:57:00 +0200
From: Paul van Hoven <paul.van.hoven@...glemail.com>
To: john-users@...ts.openwall.com
Subject: Re: Cracking Word files?
Hi! Thank you for all your answers. The first thing to say is that I
use Mac OS X Lion. Therefore I was not able to use the Windows
binaries. Anyway the page posted by Rich contained some oder binaries
for mac but this archive does not contain the office2john file.
@Dhiru
Thank you for that link. I already read this instructions before. But
since I do not use linux, these instructions weren't that helpful,
sorry.
However, I tried to compile it in a virtual machine running ubuntu. I
downloaded the packages you described in you instruction manual and
also downloaded magnumripper from the git repository. Then I changed
into src and entered make office2john. Maybe the result interests you:
parallels@...ntu:~/Downloads/magnumripper-magnum-jumbo-47a6d4e/src$
make office2john
gcc `xml2-config --cflags` `pkg-config --cflags libgsf-1`
office2john.c common.o base64.o `pkg-config --libs libgsf-1`
`xml2-config --libs` -o ../run/office2john
gcc: common.o: No such file or directory
gcc: base64.o: No such file or directory
In file included from office2john.c:69:0:
common.h:13:18: fatal error: arch.h: No such file or directory
compilation terminated.
make: *** [office2john] Error 1
Back to my problem: What do I have to do to get office2john running on my mac?
Thx,
Paul
2012/7/9 Rich Rumble <richrumble@...il.com>:
> On Mon, Jul 9, 2012 at 1:11 AM, Dhiru Kholia <dhiru.kholia@...il.com> wrote:
>> On Sun, Jul 8, 2012 at 11:49 PM, Rich Rumble <richrumble@...il.com> wrote:
>>> office2john.exe c:\path\to\office_file.doc >output.txt
>>> That should echo a sting like this into a file called output.txt.
>>
>> On Windows, instead of doing "office2john.exe
>> c:\path\to\office_file.doc >output.txt" *do* "office2john.exe
>> office_file.doc >output.txt". The former command causes colon (":") to
>> be introduced in output.txt, which will result in john not loading the
> Seems like the logic should count colon's or separators from right to
> left as opposed to left to right, is that an easy and or proper
> solution? That or we probably have to make warnings or documentation
> about such issues. Perhaps other *2john programs need to read R to L
> as well...
> -rich
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.
