From: desrt <desrt@desrt.ca>
To: linux-kernel@vger.kernel.org
Subject: linux 2.5: crypto core + block devices + ???
Date: 18 Feb 2003 22:37:05 -0500 [thread overview]
Message-ID: <1045625825.2879.8.camel@nothing.desrt.ca> (raw)
Hi.
I've recently been poking around the 2.5 source tree. I've noticed that
we now have crypto built into the stock kernel distribution (good). The
loopback driver doesn't appear to support using the crypto API though.
(bad)
Looking at the way the crypto api works (ie: skatterlists) makes it seem
vaguely compatible with what I've read about the new block device IO
mechanisms in 2.5. Is this an accident? Is there some generic crypto
support for block devices planned that will obsolete using the loopback
driver to this end? (like the pages get decrypted upon loading into the
buffer cache from the physical media or whatever? i'm not really sure
how all the block device stuff works,...)
If there are no deeper motives here and the intention is to continue
supporting encrypted filesystems via the loopback interface, is there
anyone working on the project? It seems a little bit slow (or
uncertain) with respects to the 2.5 kernels. If somebody is needed to
write some code, I'd be willing to write a loopback transfer function to
interact with the crypto core. (I'd have no idea where to start for the
generic block device crypto ramblings mentioned above...)
Anyway.. thanks in advance. Please CC replies to my address as I'm not
a list member.
Ryan
next reply other threads:[~2003-02-19 3:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 3:37 desrt [this message]
2003-02-19 3:56 ` linux 2.5: crypto core + block devices + ??? James Morris
2003-02-19 18:41 ` Jari Ruusu
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=1045625825.2879.8.camel@nothing.desrt.ca \
--to=desrt@desrt.ca \
--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