DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Jamaal Speights <jamaal.speights@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptesetup remove question
Date: Tue, 30 Mar 2010 00:59:51 +0200	[thread overview]
Message-ID: <4BB130E7.9060007@redhat.com> (raw)
In-Reply-To: <8a87818a1003291321m7dab4418pa046f6667245a79a@mail.gmail.com>

On 03/29/2010 10:21 PM, Jamaal Speights wrote:
> When I do dmsetup table [name] --showkey
> 
> I see aes-cbc-plain.  Then 64 characters.  I see the first 40 are the
> *RIPEMD-160 Hash* of my password.  What are the last 24 characters? 
> 
> ripemd160_passphrase + ?????? 

you mean after plain create command (iow not using LUKS?)

The key is generated by hashing passphrase in rounds,
so first is plain hash of passphrase (default is ripemd160),
if requested key is larger some fixed chars are added to password
and it is hashed again.
(I think it is taken from hashalot package.)

See gcrypt_hash in source, it is original algorithm
from old cryptsetup.

Or you can use pregenerated key in plain mode from keyfile.
Or you can use passphrase directly as key (zero padded)
See man page.

LUKS generates master key always from RNG, passphrase just
unlock key slot where it is stored.

Milan

  parent reply	other threads:[~2010-03-29 22:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 23:38 [dm-crypt] cryptesetup remove question Jamaal Speights
2010-03-26  8:58 ` Milan Broz
2010-03-29 20:21   ` Jamaal Speights
2010-03-29 21:41     ` Arno Wagner
2010-03-29 22:59     ` Milan Broz [this message]
2010-03-30 18:52       ` [dm-crypt] device-mapper: remove ioctl failed: Device or resource busy Ali Reza Sajedi
2010-03-30 19:43         ` Milan Broz

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=4BB130E7.9060007@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=jamaal.speights@gmail.com \
    /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