From: Andrea Arcangeli <andrea@suse.de>
To: Herbert Valerio Riedel <hvr@hvrlab.org>
Cc: linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: RFC: block/loop.c & crypto
Date: Mon, 23 Jul 2001 00:21:58 +0200 [thread overview]
Message-ID: <20010723002158.A23517@athlon.random> (raw)
In-Reply-To: <20010722170313.B30813@athlon.random> <Pine.LNX.4.33.0107222031390.3517-100000@janus.txd.hvrlab.org>
In-Reply-To: <Pine.LNX.4.33.0107222031390.3517-100000@janus.txd.hvrlab.org>; from hvr@hvrlab.org on Sun, Jul 22, 2001 at 08:53:50PM +0200
On Sun, Jul 22, 2001 at 08:53:50PM +0200, Herbert Valerio Riedel wrote:
> I haven't told you how the cryptoloop.c module contains the necessary
> logic... :-)
I see now ;).
> security is not the issue; it's more of practical terms... since 512 byte
> seems to be the closest practical transfer size (there isn't any smaller
> blocksize supported with linux) it seems natural to use that one....
to me it sounds more natural to use the 1k blocksize that seems to be
backwards compatible automatically (without the special case), the only
disavantage of 1k compared to 512bytes is the decreased security, so if
the decreased security is not your concern I'd suggest to use the 1k
fixed granularity for the IV. 1k is also the default BLOCK_SIZE I/O
granularity used by old linux (which incidentally is why it seems
backwards compatible automatically).
Andrea
next prev parent reply other threads:[~2001-07-22 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-22 10:21 RFC: block/loop.c & crypto Herbert Valerio Riedel
2001-07-22 15:03 ` Andrea Arcangeli
2001-07-22 18:53 ` Herbert Valerio Riedel
2001-07-22 22:21 ` Andrea Arcangeli [this message]
2001-07-23 1:47 ` Albert D. Cahalan
2001-07-23 2:08 ` Andrea Arcangeli
[not found] <20010723170038.G822@athlon.random>
2001-07-24 9:56 ` Herbert Valerio Riedel
2001-07-25 20:28 ` Andrea Arcangeli
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=20010723002158.A23517@athlon.random \
--to=andrea@suse.de \
--cc=axboe@suse.de \
--cc=hvr@hvrlab.org \
--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