From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tazok.id0@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 elansvl_UePa for <dm-crypt@saout.de>;
 Fri,  7 Dec 2012 20:28:31 +0100 (CET)
Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42])
 (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>; Fri,  7 Dec 2012 20:28:31 +0100 (CET)
Received: by mail-wg0-f42.google.com with SMTP id dr1so990522wgb.1
 for <dm-crypt@saout.de>; Fri, 07 Dec 2012 11:28:30 -0800 (PST)
Message-ID: <50C24385.6030609@gmail.com>
Date: Fri, 07 Dec 2012 20:29:09 +0100
From: =?ISO-8859-1?Q?Javier_Juan_Mart=EDnez_Cabez=F3n?= <tazok.id0@gmail.com>
MIME-Version: 1.0
References: <20121206152945.GA21779@tansi.org>
In-Reply-To: <20121206152945.GA21779@tansi.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] FAQ Montly pointer 12/2012
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@saout.de

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/12/12 16:29, Arno Wagner wrote:
> Updates: Added a passphrase strength estimate based on 
> http://it.slashdot.org/story/12/12/05/0623215/new-25-gpu-monster-devours-strong-passwords-in-minutes
>
>  Executive summary: It may be time to increase passphrase length.
> 
> -----
> 
> The FAQ can be found at -
> http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions 
> and - in the sources as FAQ in the top-level directory.
> 



This is applicable if the algoritm used to cipher is unknown as happen
in plain dmcrypt?


Arno, is really useful/secure to get the ciphering algoritm in the
LUKS header?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJQwkODAAoJEFfmTgt/w77fw2UP/jdGU2TjX78JpJAn/xPG2zyz
ypKRcqCSzd275Ssf5Q+c7D8pWx5g3Dd1bwJJuSBIgoSrZF6UP2mm/RJ0OrX7OTD6
xhHJEyhx4a+PxYj/fSNqdK165DrXrBExons7hloEPi7wKLMa9heESVkjEm0VNRE+
JjUOmDwAS7gHFw+/tDID4HI5Grson9Sa3QfcPD48ZeS+vdcGHW6ge++t4i8r+iXK
57XsN9bbKnIA2mx2J1FazxnE8f2TiA343xJs9cG2nuVsahlgqX29nwFbRA8wfoP9
aSSxN4tshaLEDDzVlzec2rYKCW+VAaPxixvMkpR50HiDbVRn3XnAB+I84RUG4zZ1
H1pi44ZT5qUpm2sexVJ0KgRvIfno/JUvjTMQ8tLkU1Si/i8o9uF7Kgpzfpy4lUY3
/YceOsyT0FHL17qmQoKRsVB2QLkxnb0YOI4D9NMi5rsB9R7/4N1kddVFyXji9812
jC27hEtDthQQymKEd11OBZipm1SL5OuFhIiYs/LHko/W2BFoTgVYpHf9nx5udpJ+
/MjGHcT0xOd6Wm+5OM4738wmDtkC3C0MpFKYKANVy22lvIHFlFEBfV1KBaEHTEpD
AH13OVM9k6eUP20cE84heldlIkgsGwnLJegNxFNTdXQ4U6bqfzM5lgLjsmRXvAqr
ROry+/hl+k13wE/ogtOY
=RCwp
-----END PGP SIGNATURE-----