From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: David Miller <davem@davemloft.net>
Cc: gautam.singaraju@gmail.com, linux-crypto@vger.kernel.org
Subject: Re: RSA support into kernel?
Date: Fri, 6 Jul 2007 16:10:51 +0400 [thread overview]
Message-ID: <20070706121050.GA9721@2ka.mipt.ru> (raw)
In-Reply-To: <20070706.040533.30182871.davem@davemloft.net>
On Fri, Jul 06, 2007 at 04:05:33AM -0700, David Miller (davem@davemloft.net) wrote:
> From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
> Date: Fri, 6 Jul 2007 14:37:31 +0400
>
> > On Thu, Jul 05, 2007 at 03:48:51PM -0700, Gautam Singaraju (gautam.singaraju@gmail.com) wrote:
> > > Is there any attempts being made to provide software based RSA
> > > cryptographic support in kernel level? I see that 2.6.21 supports
> > > Hardware devices such as VIA Padlock ACE. Has anybody had a change to
> > > use such a system?
> >
> > VIA padlock engine or RSA? The former is heavily used in the wild, but
> > why would anyone want to use RSA in the kernel?
>
> Automatic SSL done in-kernel on user data for socket I/O, with
> hardware offload from the crypto layer when available.
>
> Solaris has done this for quite some time and it helps a lot for
> things like the VIA and Niagara.
I.e. for userspace stuff? That is obviously the right usage, but Linux
cryptoapi does not have userspace interface, so was my question.
Actually I was several times already asked after acrypto was closed, how
userspace can use new hardware drivers, and frankly I do not know what
the best userspace API would look like (in one of the projects I already
used all three methods one-by-one and failed to determine the best).
Simple char device read/write or ioctl, or blocking/nonblocking syscall
over file descriptor, or anything else?
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-07-06 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 22:48 RSA support into kernel? Gautam Singaraju
2007-07-06 10:37 ` Evgeniy Polyakov
2007-07-06 11:05 ` David Miller
2007-07-06 12:10 ` Evgeniy Polyakov [this message]
2007-07-06 13:12 ` Herbert Xu
2007-07-06 13:36 ` Michael Halcrow
2007-07-06 14:41 ` Gautam Singaraju
2007-07-06 15:41 ` Michael Halcrow
2007-07-06 17:23 ` Gautam Singaraju
2007-07-06 16:01 ` Herbert Xu
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=20070706121050.GA9721@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=davem@davemloft.net \
--cc=gautam.singaraju@gmail.com \
--cc=linux-crypto@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