From: felix@crowfix.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Script to crack gpg passphrase
Date: Wed, 27 Apr 2011 11:15:46 -0700 [thread overview]
Message-ID: <20110427181546.GA19893@crowfix.com> (raw)
In-Reply-To: <201104262124.55281.michaelkintzios@gmail.com>
On Tue, Apr 26, 2011 at 09:24:44PM +0100, Mick wrote:
> Back to plan A. Any ideas how I can improve my script?
Do you have any guesses as to your passphrase or is it a total shot in
the dark, could be anything from one word to a poem?
Unless you can narrow it down tremendously, you're wasting time and it
will never be recovered.
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
next prev parent reply other threads:[~2011-04-27 18:17 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 [this message]
2011-04-27 18:56 ` Mick
2011-04-28 14:04 ` Mick
2011-04-28 16:47 ` Michael Orlitzky
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=20110427181546.GA19893@crowfix.com \
--to=felix@crowfix.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