Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 1 Jul 2012 12:40:56 +0530
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Significant items concerning the MS Windows (cygwin)
 build of john-1.7.9-jumbo-6

On Sun, Jul 1, 2012 at 12:16 PM, Robert B. Harris <rs904c@...scape.net> wrote:
> July 1, 2012 significant items concerning the MS Windows (cygwin) build of
> john-1.7.9-jumbo-6:
> -I think I may have found a bug/issue when using office2john, when including
> a path to the input file.
>
> In other words: office2john C:\#dev\s.docx > C:\#dev\s.txt
>
>
>
> type C:\#dev\s.txt
>
> C:\#dev\s.docx:$office$*2007*20*128*16*12578ade7b6e20076c1007d69407e5ea*a47ca2e1255df2e2dfabd9dc24681e47*3b2ac2fcde95f130938eb2e9edc7a0518a67ee7643753bc27b1aceb4f6c2feec
>
>
>
> John will error with the s.txt file above, and say no hashes were found.
>
> When the path is removed from within the s.txt file, John recognizes the
> hash.

The colon (":") in the path is causing john to fail. I can internally
convert the colon to something else to prevent the failure. This is be
a common problem with almost all non-hash formats when running under
Windows (which uses colon in the path name).

-- 
Cheers,
Dhiru

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ