From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <wagner@tansi.org>
Received: from tansi.org (ns.km10532-04.keymachine.de [87.118.102.195])
	by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Mon, 29 Mar 2010 23:39:51 +0200 (CEST)
Received: from gatewagner.dyndns.org (84-74-164-239.dclient.hispeed.ch
	[84.74.164.239]) by tansi.org (Postfix) with ESMTPA id 3AA731218177
	for <dm-crypt@saout.de>; Mon, 29 Mar 2010 23:39:51 +0200 (CEST)
Date: Mon, 29 Mar 2010 23:41:52 +0200
From: Arno Wagner <arno@wagner.name>
Message-ID: <20100329214152.GA20026@tansi.org>
References: <8a87818a1003251638m5f6fbf85v23545f5acad506e4@mail.gmail.com>
	<4BAC774B.5060802@redhat.com>
	<8a87818a1003291321m7dab4418pa046f6667245a79a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8a87818a1003291321m7dab4418pa046f6667245a79a@mail.gmail.com>
Subject: Re: [dm-crypt] cryptesetup remove question
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

Without checking: The salt?

Arno


On Mon, Mar 29, 2010 at 04:21:41PM -0400, Jamaal Speights wrote:
> Thanks.
> 
> 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 + ??????
> 
> thanks
> 
> -j
> 
> 
> On Fri, Mar 26, 2010 at 4:58 AM, Milan Broz <mbroz@redhat.com> wrote:
> 
> > On 03/26/2010 12:38 AM, Jamaal Speights wrote:
> > > I am curious about the cryptsetup remove function and its purpose after
> > > rebooting a system.  Is my system still vulnerable to someone else
> > > mounting my encrypted file if I don't remove the mapping before I
> > > reboot?  When my system comes back up I don't see the mapping in
> > > /dev/mapping/cryptfile  .  Also if I do cryptsetup to mount the image
> > > again I have to re-enter the password.  So whats the point of using
> > > cryptsetup remove when shutting your system down?
> >
> > Remove key from memory? (google coldboot attack)
> >
> > Deactivate crypt mapping so underlying storage can safely deactivate
> > devices (LVM for example)?
> >
> > Umount underlying filesystem if mappping is to file on it?
> >
> > ...
> >
> > Milan
> >

> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt


-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier