public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Script to crack gpg passphrase
Date: Thu, 28 Apr 2011 12:47:54 -0400	[thread overview]
Message-ID: <4DB99A3A.3050903@orlitzky.com> (raw)
In-Reply-To: <BANLkTi=UkxofbPrOZGVuyS3TWaBpPeMUkA@mail.gmail.com>

On 04/28/2011 10:04 AM, Mick wrote:
> This finds the passphrase and prints it out on the terminal.  However, its
> success depends on the dictionary file I use.  Also, it's not particularly
> fast ...
> 
> Any idea how I can create a dictionary file?  I've used apg but it's <aheam!>
> too random.  :-)
> 
> I have been given something like 6 passphrases that may have been used.  The
> problem is that at the time of creation the passphrase was typed in
> incorrectly (twice!)  So I would need to use some method of generating a
> dictionary with potential typos of these known passphrases (pretty much how
> the rephrase application works).  What is a good way to generate such a file
> by imputing a range of candidate characters?
> 
> Finally, is there a way or parallelising the run so that it speeds up?
> 

If you know the actual passphrase is "close" to some known passphrase,
read up on the concept of Levenshtein distance:

  http://en.wikipedia.org/wiki/Levenshtein_distance

If you can define a function that computes all passwords of Levenshtein
distance 1 from a given password, then you can run that function twice
to get the password of distance 2,3... Three or four is probably a good
place to stop.

Then you can take those six known passwords, and compute all words of
distance 1,2,3 from all of them. Stick those in a list, and try them.



      reply	other threads:[~2011-04-28 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 14:20 [gentoo-user] [OT] Script to crack gpg passphrase Mick
2011-04-26 14:34 ` Paul Hartman
2011-04-26 15:42   ` Mick
2011-04-26 20:24     ` Mick
2011-04-27 18:15       ` felix
2011-04-27 18:56         ` Mick
2011-04-28 14:04           ` Mick
2011-04-28 16:47             ` Michael Orlitzky [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DB99A3A.3050903@orlitzky.com \
    --to=michael@orlitzky.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox