From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] Forgot dm-crypt password; suggestions on steps to undertake
Date: Tue, 12 Nov 2013 16:10:53 +0100 [thread overview]
Message-ID: <528244FD.4060109@gmail.com> (raw)
In-Reply-To: <52824219.1010607@0x01b.net>
On 11/12/2013 03:58 PM, Matthew Monaco wrote:
> It didn't make sense to me to do it using libcryptsetup because the bottleneck
> was the actual decryption attempt.
The example I posted link to is using common context and arbitrary number
of processes (default is number of CPU cores) which run in parallel
(hash iterations can easily run in parallel on different CPUs)
So every process tries n-th line in candidate password file.
This is the advantage (plus save some negligible initialization time),
otherwise script is fine of course.
Milan
next prev parent reply other threads:[~2013-11-12 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 21:48 [dm-crypt] Forgot dm-crypt password; suggestions on steps to undertake John Thoe
2013-11-09 22:51 ` Arno Wagner
2013-11-10 0:15 ` John Thoe
2013-11-10 1:03 ` Milan Broz
2013-11-10 16:26 ` Arno Wagner
2013-11-11 2:25 ` John Thoe
2013-11-11 3:13 ` Arno Wagner
2013-11-11 5:51 ` Milan Broz
2013-11-12 14:58 ` Matthew Monaco
2013-11-12 15:10 ` Milan Broz [this message]
2013-11-12 18:56 ` Matthew Monaco
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=528244FD.4060109@gmail.com \
--to=gmazyland@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox