From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] LUKS & search for passphrase using dictionary
Date: Fri, 20 Jul 2012 00:48:17 +0200 [thread overview]
Message-ID: <50088EB1.4090403@gmail.com> (raw)
Hi,
From time to time someone tries to recover (or crack) LUKS passphrase
using dictionary lists.
I saw lately even some crazy patches for cryptsetup doing that.
Please do not patch source or create some slow bash scripts
(initialization and memory locking cost resources).
Just use libcryptsetup. I added some example how to do it, see
http://code.google.com/p/cryptsetup/source/browse/#git%2Fmisc%2Fdict_search
e.g. for JTR known password list you can run (on quadcore cpu here)
# luks_dict test.img /usr/share/john/password.lst 4
Then read FAQ how LUKS keyslot iterations slow down these attacks...
It is just quickly written example, perhaps with some bugs.
Anyway, enjoy :)
Milan
p.s.
If you really run this, compile cryptsetup with openssl support
(configure --with-crypto_backend=openssl) it is quicker than default gcrypt.
next reply other threads:[~2012-07-19 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 22:48 Milan Broz [this message]
2012-07-19 23:34 ` [dm-crypt] LUKS & search for passphrase using dictionary 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=50088EB1.4090403@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 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.