From: "Javier Juan Martínez Cabezón" <tazok.id0@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] FAQ Montly pointer 12/2012
Date: Fri, 07 Dec 2012 20:29:09 +0100 [thread overview]
Message-ID: <50C24385.6030609@gmail.com> (raw)
In-Reply-To: <20121206152945.GA21779@tansi.org>
-----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-----
next prev parent reply other threads:[~2012-12-07 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 15:29 [dm-crypt] FAQ Montly pointer 12/2012 Arno Wagner
2012-12-07 19:29 ` Javier Juan Martínez Cabezón [this message]
2012-12-07 19:57 ` 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=50C24385.6030609@gmail.com \
--to=tazok.id0@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