[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 2 Sep 2012 01:29:03 +0200
From: Paul van Hoven <paul.van.hoven@...glemail.com>
To: john-users@...ts.openwall.com
Subject: Re: Cracking Word files?
Sorry for not having answered so long. I now had again time to try the
compilation of office2john. On my Ubunut Natty installation I altered
the code of office2john.c back from mkdtemp to mktemp. Then I again
executed the following commands on the console
make clean linux-x86-64 (works fine)
make office2john
I get the follwing compilation error
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
/tmp/ccbohS5F.o: In function `test':
office2john.c:(.text+0xdf2): warning: the use of `mktemp' is
dangerous, better use `mkstemp' or `mkdtemp'
This is where the compilation stops.
2012/8/8 Dhiru Kholia <dhiru.kholia@...il.com>:
> On Wed, Aug 8, 2012 at 5:07 AM, Solar Designer <solar@...nwall.com> wrote:
>> On Tue, Aug 07, 2012 at 03:00:14AM +0200, Paul van Hoven wrote:
>>> A small hint: I had to replace mktemp by mkdtemp in office2john.c in
>>> order to get the file compiled.
>>
>> What error were you getting when trying to compile the original code?
>> (I am aware that some systems now print deprecation warnings or even
>> errors about mktemp(), but I thought Ubuntu was not one of those where
>> mktemp() was treated as a fatal error.)
>
> office2john.c works fine on CentOS 6.2 and Arch Linux without any changes.
>
> Please post the errors you got when compiling under Ubuntu.
>
>>> parallels@...ntu:~/Downloads/magnumripper-magnum-jumbo-47a6d4e/run$
>>> ./office2john /media/psf/Home/Downloads/TestEncrypted.docx
>
> I could successfully crack this file with JtR. No problems.
>
>>> /media/psf/Home/Downloads/TestEncrypted.docx : office2johntNuMqb: File exists
>> I think this is a consequence of your source code change above - perhaps
>> your code, with the change, tries to create the directory twice.
>
> I too think so.
>
>> Dhiru - I think it'd be best to write cleaner C code rather than rewrite
>> this in Python (as you said you were going to), unless you have a
>> specific reason for that rewrite (e.g., some needed library only easily
>> available from Python).
>
> I could not figure out how to use libxml without giving it a file name
> to operate on. Python libraries are easier to use and using them won't
> involve dirty hacks.
>
> --
> 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.
