From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Question on LUKS master key digest and its effect on security
Date: Sat, 19 Sep 2009 18:51:48 +0200 [thread overview]
Message-ID: <20090919165148.GA5619@fancy-poultry.org> (raw)
In-Reply-To: <4AB3CE76.5040502@redhat.com>
On 18.09.2009, Milan Broz wrote:
> Yes it was hardcoded to use sha1. But it is no longer true anyway.
> Using another hash (all algorithms provided by libgcrypt) is already
> implemented in devel code.
As reported some weeks ago, the buffer i/o errors are still present with
the latest svn code (from today):
[....]
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 32
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 4
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 5
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 6
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 7
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 8
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 9
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 10
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 11
Sep 19 18:35:57 liesel kernel: __ratelimit: 37 callbacks suppressed
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 64
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 65
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 64
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 65
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 120
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 121
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 120
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 121
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 8
[....]
cryptsetup-1.0.7 works fine.
next prev parent reply other threads:[~2009-09-19 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 17:39 [dm-crypt] Question on LUKS master key digest and its effect on security Tero Pesonen
2009-09-18 18:16 ` Milan Broz
2009-09-18 20:18 ` Tero Pesonen
2009-09-22 15:08 ` Tero Pesonen
2009-09-22 15:47 ` Milan Broz
2009-09-22 17:47 ` Tero Pesonen
2009-09-22 16:14 ` [dm-crypt] Question on LUKS master key digest and its effect on?security Heinz Diehl
2009-09-22 16:21 ` Milan Broz
2009-09-19 16:51 ` Heinz Diehl [this message]
2009-09-19 19:00 ` [dm-crypt] Question on LUKS master key digest and its effect on security Milan Broz
2009-09-20 11:28 ` Heinz Diehl
2009-09-20 15:09 ` Heinz Diehl
2009-09-20 18:11 ` Milan Broz
2009-09-20 21:03 ` Heinz Diehl
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=20090919165148.GA5619@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox