From: Jeff Garzik <jgarzik@pobox.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: Michael Halcrow <mahalcro@us.ibm.com>,
CryptoAPI List <cryptoapi@lists.logix.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /dev/crypto for Linux
Date: Wed, 25 Aug 2004 10:17:45 -0400 [thread overview]
Message-ID: <412C9F89.7000901@pobox.com> (raw)
In-Reply-To: <412C41BC.8020607@suse.cz>
> What is it good for?
> One can build really light-weigth programs with crypto support that
> don't need any external libraries (e.g. OpenSSL) or built-in algorithms.
> Easier testing of new CryptoAPI ciphers (later also hashes and maybe
> asymmetric ciphers as well).
> Once, maybe, userspace access to crypto accelerators through kernel
> drivers.
Let's see...
1) This increases context switches over a solution that links with
libcrypto and libssl.
2) "build really lightweight programs with crypto support" implies that
you think it's a benefit to use the kernel as your crypto lib. Shared libs
3) Your proposal actually avoids existing, working hardware crypto
support such as Broadcom's hwcrypto driver which is fully supported by
openssh.
4) "open it and use ioctls to transfer data" is typically a bad idea.
ioctl(2) is a historical Unix mistake, to be avoided where possible.
read(2)/write(2) are to be used to transfer data.
Jeff
next prev parent reply other threads:[~2004-08-25 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 21:37 [PATCH] /dev/crypto for Linux Michal Ludvig
[not found] ` <20040824215351.GA9272@halcrow.us>
2004-08-25 7:37 ` Michal Ludvig
2004-08-25 14:17 ` Jeff Garzik [this message]
2004-08-25 14:41 ` Michal Ludvig
2004-08-25 14:26 ` Christoph Hellwig
2004-08-25 15:44 ` Michal Ludvig
2004-08-25 14:42 ` Christoph Hellwig
2004-08-25 14:44 ` James Morris
2004-08-25 21:28 ` Bill Davidsen
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=412C9F89.7000901@pobox.com \
--to=jgarzik@pobox.com \
--cc=cryptoapi@lists.logix.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mahalcro@us.ibm.com \
--cc=mludvig@suse.cz \
/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