From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] RC1/2 misbehaviour (bug?)
Date: Fri, 09 Oct 2009 14:04:01 +0200 [thread overview]
Message-ID: <87pr8wlqoe.wl%htd@fancy-poultry.org> (raw)
In-Reply-To: <4ACF14CE.1060802@redhat.com>
At Fri, 09 Oct 2009 12:47:42 +0200,
Milan Broz wrote:
> Run cryptsetup with --debug and also check syslog and you will see that it retries
> the remove.
Did it, you're right.
> You will probably find error that temporary-cryptsetup-$PID device is open and cannot
> be removed. Please report it to your distro as bug, you will need check who opened
> this device (I guess it is blkid from some generic udev rule)
Yes, I've seen this too. I'm on opensuse 11.1.
> Maybe I should add some message to debug about proces name opening that internal device...
That would be helpful, thanks!
> Note that it is possible security problem - keystore device contains hashed master
> key, no other process except cryptsetup should read that (and store anywhere in
> unlocked memory).
This is ugly as hell. I will report this to the opensuse people and try to fix
this immediately on my system.
Thanks,
Heinz.
prev parent reply other threads:[~2009-10-09 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 7:47 [dm-crypt] RC1/2 misbehaviour (bug?) Heinz Diehl
2009-10-09 10:47 ` Milan Broz
2009-10-09 12:04 ` Heinz Diehl [this message]
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=87pr8wlqoe.wl%htd@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--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.