From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Jari Ruusu <jariruusu@users.sourceforge.net>
Cc: James Morris <jmorris@redhat.com>,
Jean-Luc Cooke <jlcooke@certainkey.com>,
Christophe Saout <christophe@saout.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: dm-crypt, new IV and standards
Date: Sat, 21 Feb 2004 01:31:46 +0100 [thread overview]
Message-ID: <4036A6F2.60907@gmx.net> (raw)
In-Reply-To: <Xine.LNX.4.44.0402201624030.7335-100000@thoron.boston.redhat.com>
Jari,
since mainline cryptoloop/dm-crypt implementation is being changed right
now and you were complaining about it in the past, can you participate in
the discussions (there's also a parallel thread titled "[PATCH/proposal]
dm-crypt: add digest-based iv generation mode") so you don't have to
complain afterwards?
James Morris wrote:
> On Fri, 20 Feb 2004, Jean-Luc Cooke wrote:
>
>
>>If others on the list care to do this, I'll give recommendation on how to
>>implement the security (hmac, salt, iteration counts, etc). But I think
>>this may break backward compatibility. Can anyone speak to this?
>
>
> Please focus your recommendations on security, not backward compatibility
> with something that is new to the kernel tree, broken and maintainerless.
Thanks,
Carl-Daniel
next prev parent reply other threads:[~2004-02-21 0:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 22:06 dm-crypt, new IV and standards Carl-Daniel Hailfinger
2004-02-19 22:20 ` Christophe Saout
2004-02-20 17:22 ` Jean-Luc Cooke
2004-02-20 21:26 ` James Morris
2004-02-20 21:52 ` 2.6.3 adaptec I2O will not compile David Lang
2004-02-25 16:25 ` Adrian Bunk
2004-02-26 8:02 ` Jaco Kroon
2004-02-26 8:08 ` David Lang
2004-02-26 9:28 ` Jaco Kroon
2004-02-26 10:24 ` David Lang
2004-02-21 0:31 ` Carl-Daniel Hailfinger [this message]
2004-02-21 16:48 ` dm-crypt, new IV and standards Jean-Luc Cooke
2004-02-21 17:36 ` Jean-Luc Cooke
2004-02-21 19:01 ` Andreas Jellinghaus
2004-03-03 8:35 ` dean gaudet
2004-03-03 15:06 ` Jean-Luc Cooke
2004-03-03 21:40 ` David Wagner
2004-03-08 19:58 ` Jean-Luc Cooke
2004-03-04 1:48 ` dean gaudet
2004-03-04 13:24 ` Jean-Luc Cooke
2004-03-04 17:44 ` David Wagner
2004-03-05 1:19 ` dean gaudet
2004-03-05 2:14 ` Jean-Luc Cooke
2004-03-04 15:08 ` Pavel Machek
2004-03-07 4:14 ` DM for detecting bad disks was: " Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2004-02-22 19:20 Adam J. Richter
2004-02-22 20:53 ` Christophe Saout
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=4036A6F2.60907@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=akpm@osdl.org \
--cc=christophe@saout.de \
--cc=jariruusu@users.sourceforge.net \
--cc=jlcooke@certainkey.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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