From: "Serge E. Hallyn" <serue@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: Joy Latten <latten@austin.ibm.com>
Subject: Re: RSA
Date: Tue, 15 Jun 2004 19:54:09 -0400 [thread overview]
Message-ID: <20040615235409.GA12186@escher.cs.wm.edu> (raw)
In-Reply-To: <Xine.LNX.4.44.0406142127240.25480-100000@thoron.boston.redhat.com>
(repeating a privately posted question for all to respond)
Is a separate generic assymetric crypto API really necessary?
The cryptoapi usage model is to do a setkey before any encrypt or decrypt.
The setkey will be done with either a public or private key. So there is no
need to have a public_key_alg with separate public_encrypt and
private_encrypt functions, as this distinction is implied at the setkey
time. So our plan was to just add another crypto_alg for rsa_1024.
If anyone can point out why this is insufficient, then we will certainly
reconsider.
thanks,
-serge
Quoting James Morris (jmorris@redhat.com):
> On Tue, 15 Jun 2004, Joy Latten wrote:
>
> > Is anyone working on implementing RSA encryption/decryption into the
> > kernel's cryptoapi? If not, I was considering starting such a project.
>
> Not that I know of. Would you be looking at this in terms of a generic
> asymmetric crypto API?
>
>
> - James
> --
> James Morris
> <jmorris@redhat.com>
next prev parent reply other threads:[~2004-06-15 23:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 9:44 RSA Joy Latten
2004-06-15 1:29 ` RSA James Morris
2004-06-15 23:54 ` Serge E. Hallyn [this message]
2004-06-16 0:22 ` RSA tom st denis
2004-06-16 2:04 ` RSA Serge E. Hallyn
2004-06-16 2:52 ` RSA tom st denis
2004-06-19 16:12 ` RSA Kristian Sørensen
2004-06-15 16:46 RSA kartikey bhatt
2004-06-19 2:56 RSA Joy Latten
2004-06-19 4:37 RSA kartikey bhatt
2004-06-22 4:13 RSA kartikey bhatt
2004-06-22 11:52 ` RSA tom st denis
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=20040615235409.GA12186@escher.cs.wm.edu \
--to=serue@us.ibm.com \
--cc=latten@austin.ibm.com \
--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®