mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Saout <christophe@saout.de>
To: Pascal Brisset <pascal.brisset-ml@wanadoo.fr>
Cc: Fruhwirth Clemens <clemens-dated-1061346967.29a4@endorphin.org>,
	linux-kernel@vger.kernel.org, mbligh@aracnet.com,
	kernel@gozer.org, axboe@suse.de
Subject: Re: [PATCH] loop: fixing cryptoloop troubles.
Date: Sun, 10 Aug 2003 16:27:47 +0200	[thread overview]
Message-ID: <1060525667.14835.4.camel@chtephan.cs.pocnet.net> (raw)
In-Reply-To: <20030810140912.6F7224007E9@mwinf0301.wanadoo.fr>

Am So, 2003-08-10 um 16.10 schrieb Pascal Brisset:

> > In loop_transfer_bio the initial vector has been computed only once. For any
> > situation where more than one bio_vec is present the initial vector will be
> > wrong. Here is the trivial but important fix. 
> 
> Looks good, but:
> - I doubt this could explain the alteration pattern (1 byte every 512).
> - Corruption also occured with cipher_null (which ignores the IV).

I personally think that the only way to get things right is to do
encryption sector by sector (not bvec by bvec) since every sector can
have its own iv.

I've implemented a crypto target for device-mapper that does this and it
doesn't seem to suffer from these corruption problems:
http://marc.theaimsgroup.com/?l=linux-kernel&m=105967481007242&w=2 and a
slightly updated patch: http://www.saout.de/misc/dm-crypt.diff

Unfortunately I haven't got a single response. :(

Just got one person outside LKML to (successfully) test it.

Should I repost the patch (inline this time) with an additional [PATCH]
or am I being annoying? Joe Thornber (the dm maintainer) would like to
see this patch merged.

--
Christophe Saout <christophe@saout.de>
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html


  reply	other threads:[~2003-08-10 14:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10  2:36 Fruhwirth Clemens
2003-08-10 14:10 ` Pascal Brisset
2003-08-10 14:27   ` Christophe Saout [this message]
2003-08-10 21:03     ` Fruhwirth Clemens
2003-08-10 22:07       ` Christophe Saout
2003-08-11 13:11         ` Fruhwirth Clemens
2003-08-11 16:16           ` Christophe Saout
2003-08-12  3:30         ` David Wagner
2003-08-10 15:15   ` James Morris
2003-08-10 16:08     ` Pascal Brisset
2003-08-10 16:28       ` James Morris
2003-08-10 18:01         ` Ingo Oeser
2003-08-11  8:38         ` Pascal Brisset
2003-08-11 13:31           ` James Morris

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=1060525667.14835.4.camel@chtephan.cs.pocnet.net \
    --to=christophe@saout.de \
    --cc=axboe@suse.de \
    --cc=clemens-dated-1061346967.29a4@endorphin.org \
    --cc=kernel@gozer.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=pascal.brisset-ml@wanadoo.fr \
    /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

Powered by JetHome