From: Michel Machado <michel@digirati.com.br>
To: Dmitry Kasatkin <dmitry.kasatkin@intel.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: RSA
Date: Thu, 11 Aug 2011 16:01:09 -0400 [thread overview]
Message-ID: <1313092869.2239.36.camel@Thor> (raw)
In-Reply-To: <4E4426CA.20209@intel.com>
Hi Dmitry,
Thanks for pointing out that patch. I does make bringing a full RSA
API into the kernel easier, but it doesn't do it. I may end up doing it
myself, and could certainly use the MPI library you're adding with that
patch, but I'd rather not since I already have a lot on my plate.
--
[ ]'s
Michel Machado
On Thu, 2011-08-11 at 22:00 +0300, Dmitry Kasatkin wrote:
> Hi,
>
> Please look to the patch just before your email...
> [RFC v1.1 2/5] crypto: ksign - digital signature verification support
>
> It implements RSA verification for IMA/EVM.
> May be it would be interesting to you.
>
> - Dmitry
>
> On 11/08/11 21:30, Michel Machado wrote:
> > Hi there,
> >
> > I'm implementing a new network stack in Linux's kernel [1], and I
> > need a RSA implementation to keep the guarantees of the design [2].
> >
> > Searching the archive of Linux's mailing lists, I've found that
> > adding RSA to the kernel has been already tried, but it was left out
> > because the uses were not convincing then.
> >
> > I intend to submit my work [3, 4] when I get a reasonable working
> > version. Until there, could anyone point me to a working patch to add
> > RSA to the kernel? The old patch [5] doesn't integrate with the current
> > Crypto API.
> >
> > Is there hope to have RSA added to Linux? If not for a ready use,
> > it'd help to experiment with things that are still in the making.
> >
> > [1] http://www.cs.cmu.edu/~xia/
> > [2] http://reports-archive.adm.cs.cmu.edu/anon/2011/CMU-CS-11-100.pdf
> > [3] git://github.com/AltraMayor/XIA-for-Linux.git
> > [4] git://github.com/AltraMayor/xiaconf.git
> > [5] http://lwn.net/Articles/228892/
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-08-11 20:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 18:30 RSA Michel Machado
2011-08-11 19:00 ` RSA Dmitry Kasatkin
2011-08-11 20:01 ` Michel Machado [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-22 4:13 RSA kartikey bhatt
2004-06-22 11:52 ` RSA tom st denis
2004-06-19 4:37 RSA kartikey bhatt
2004-06-19 2:56 RSA Joy Latten
2004-06-15 16:46 RSA kartikey bhatt
2004-06-15 9:44 RSA Joy Latten
2004-06-15 1:29 ` RSA James Morris
2004-06-15 23:54 ` RSA Serge E. Hallyn
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
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=1313092869.2239.36.camel@Thor \
--to=michel@digirati.com.br \
--cc=dmitry.kasatkin@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.