From: tesla1@gmx.net
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Recovering/Cracking passphrase
Date: Thu, 01 Jul 2010 14:34:23 +0200 [thread overview]
Message-ID: <20100701123423.326250@gmx.net> (raw)
Am Donnerstag, den 10.06.2010, 15:28 -0500 schrieb Justin Brown:
> Hello,
>
>
> I'm in a really bad situation. Basically, I've lost my passphrase, and
> I'm trying to find a way to recover it. I know what the passphrase
> should be (it's a really good 20 character passphrase), but I must
> have mistyped it when configuring cryptsetup or added some complexity
> which I failed to write down. I've tried about every combination of
> all the passwords and passphrases that I use, and I can't come up with
> anymore, so I'm going to try to build a cracker. I'd like to get some
> feedback before I put a lot of time into writing the code.
I'm in a similar situation. Luckily, the Password is only 5 characters
long.
I try a different approach. I want to use John the ripper for cracking
the password.
Therefore I want to extract the sha1 key and salt from the luks Header.
I don't know if this is possible somehow. Next I want to create a file
from that data that is understood by JTR.
To test this approach I created sha1sums with sha1sum and libssl from a
3 letter word and put them in a password file. However I wasn't able to
crack that password, even with sha1 support compiled into JTR. I guess I
don't have the correct information in the password file and/or it is
wrong formatted.
Any help and suggestions on this approach is welcome!
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
next reply other threads:[~2010-07-01 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 12:34 tesla1 [this message]
2010-07-01 13:02 ` [dm-crypt] Recovering/Cracking passphrase Roscoe
2010-07-04 17:53 ` comicinker
-- strict thread matches above, loose matches on Subject: below --
2010-06-10 20:28 Justin Brown
2010-06-10 21:02 ` Christoph Anton Mitterer
2010-06-10 21:22 ` Arno Wagner
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=20100701123423.326250@gmx.net \
--to=tesla1@gmx.net \
--cc=dm-crypt@saout.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.