From: Jon Peatfield <J.S.Peatfield@damtp.cam.ac.uk>
To: linux-kernel@vger.kernel.org
Cc: J.S.Peatfield@damtp.cam.ac.uk
Subject: crypto api stuff
Date: 16 Dec 2001 06:22:16 +0000 [thread overview]
Message-ID: <vxju1urit0n.fsf@redmires.amtp.cam.ac.uk> (raw)
In-Reply-To: Joerg Pommnitz's message of "Tue, 11 Dec 2001 12:45:22 GMT"
Having spent some time trying to decide which version of the crypto
api patch is best to apply to recent 2.4.x kernels I wondered if any
serious thought had been given to including this in the standard
kernel tree for 2.5 (and maybe some future 2.4 perhaps if it proves
stable in 2.5)?
I for one would like to take an off-the-shelf standard kernel and use
loopback to mount an encrypted file-system. Maybe then vendors would
start including this functionality.
[ I assume that the US laws on exporting crypto (which I seem to
remember got relaxed a while back) are no longer a significant
problem, or there wouldn't be things like openssl or openssh in common
distros. ]
--
Jon Peatfield, DAMTP, Computer Officer, University of Cambridge
Telephone: +44 1223 3 37852 Mail: J.S.Peatfield@damtp.cam.ac.uk
next reply other threads:[~2001-12-16 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 6:22 Jon Peatfield [this message]
2001-12-16 15:03 ` Matthew M
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=vxju1urit0n.fsf@redmires.amtp.cam.ac.uk \
--to=j.s.peatfield@damtp.cam.ac.uk \
--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
all inboxes | Powered by JetHome®