From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id NqsvapiKp1Sl for <dm-crypt@saout.de>;
 Tue, 12 Nov 2013 16:11:10 +0100 (CET)
Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com
 [IPv6:2a00:1450:4013:c01::231])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Tue, 12 Nov 2013 16:11:10 +0100 (CET)
Received: by mail-ea0-f177.google.com with SMTP id f15so3526769eak.8
 for <dm-crypt@saout.de>; Tue, 12 Nov 2013 07:11:09 -0800 (PST)
Received: from [192.168.43.92] (ip-37-188-230-33.eurotel.cz. [37.188.230.33])
 by mx.google.com with ESMTPSA id
 s3sm76944933eeo.3.2013.11.12.07.11.07 for <dm-crypt@saout.de>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Tue, 12 Nov 2013 07:11:08 -0800 (PST)
Message-ID: <528244FD.4060109@gmail.com>
Date: Tue, 12 Nov 2013 16:10:53 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <BLU181-W35325A5B76FBC4138E7AC8C9FD0@phx.gbl>,
 <20131109225126.GA8017@tansi.org>,
 <BLU181-W48EB1D9D106089FAF9A702C9FC0@phx.gbl>,
 <20131110162658.GB18656@tansi.org>
 <BLU181-W76117F145E9E68B99D5675C9FF0@phx.gbl> <52824219.1010607@0x01b.net>
In-Reply-To: <52824219.1010607@0x01b.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Forgot dm-crypt password;
 suggestions on steps to undertake
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt <dm-crypt@saout.de>

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