Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 10 Jun 2013 12:32:46 -0400
From: john ripper <not2ripped@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: gpg2john output not recognized by john

Fascinating... The bleeding edge version did in fact manage to load the
key, and is working on cracking it.  What was the problem?  Was I simply
using a version that was old and did not recognize what I was trying to
feed it?




On Mon, Jun 10, 2013 at 8:27 AM, Dhiru Kholia <dhiru.kholia@...il.com>wrote:

> On 06/09/13 at 08:29pm, john ripper wrote:
> > I am attempting to gain the key to a gpg secret key and have run into
> > a snag. John does not recognize the output from gpg2john, and gives me
> > the error "No password hashes loaded (see FAQ)." The most likely cause
> > of this is some sort of formatting issue.
>
> > In short, does anyone have any idea why on earth john cannot recognize
> > the output of this program?  What can I do to format the file so that
> > john CAN recognize it? I have tried snipping out things like the the
> > file path name, up to $gpg$ for example.
> >
> > In order to better understand the issue, and see if I could track down
> > the problem, I created a keypair using gpg with known passwords and
> > algorithm.
>
> Try these steps,
>
> 1. Get latest JtR-jumbo (bleeding-jumbo branch)
>
> git clone https://github.com/magnumripper/JohnTheRipper/ -b bleeding-jumbo
>
> cd JohnTheRipper/src
>
> 2. Build JtR as usual (make linux-x86-64)
>
> 3. ../run/gpg2john ripped.key > hash # your (sample) key
>
> 4. ../run/john hash
> Loaded 1 password hash (gpg, OpenPGP / GnuPG Secret Key [32/64])
> Press 'q' or Ctrl-C to abort, almost any other key for status
> password         (ripped.key)
>
> Good Luck!
>
> --
> 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.