From: Gary R Hook <ghook@amd.com>
To: Stephan Mueller <smueller@chronox.de>
Cc: Tadeusz Struk <tadeusz.struk@intel.com>, <linux-crypto@vger.kernel.org>
Subject: Re: Typos and RSA
Date: Wed, 18 May 2016 10:57:26 -0500 [thread overview]
Message-ID: <573C90E6.8000203@amd.com> (raw)
In-Reply-To: <6203568.4quGhfsc99@positron.chronox.de>
Ah.... enlightenment can be such an uncomfortable thing...
On 05/17/2016 05:56 PM, Stephan Mueller wrote:
> Am Dienstag, 17. Mai 2016, 17:46:44 schrieb Gary R Hook:
>
> Hi Gary,
>
>> Thanks so much.
>>
>> There are exactly 3 references to that symbol (in my freshly pulled copy
>> of cryptodev-2.6).
>> testmgr.c precipitates my questions, and public_key.c doesn't actually
>> provide any content
>> in the source input buffer, neither modulus nor plaintext. Thus, it
>> doesn't clarify things
>> either.
>>
>> But I truly appreciate your attention.
>>
>> So I'll go ahead and ask, because I did look at the two areas mentioned
>> by Stephan, but
>> neither seem to clarify (to my admittedly ignorant eyes... I'm a real
>> newbie on crypto here)
>> usage.
> Here is an example from a current code of mine (all kccavs symbols are private
> to my code):
Yes, thank you. After spending more time wandering through rsa.c &
rsa_helper.c
I have come to realize that I have been laboring under a paradigm imposed by
my implementation requirements. Now that I have that cleared up, the
answer to
my question it self-evident.Although I'm still not clear on why testmgr
feels
the need to create a SGL table with an empty second element (for the
existing
tests), rather than a single SGL. But that's neither here nor there.
As I said, I'm a newbie with lots to learn about this stuff. Thanks for your
patience.
next prev parent reply other threads:[~2016-05-18 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 21:22 Typos and RSA Gary R Hook
2016-05-17 22:16 ` Stephan Mueller
2016-05-17 22:18 ` Tadeusz Struk
2016-05-17 22:46 ` Gary R Hook
2016-05-17 22:56 ` Stephan Mueller
2016-05-18 15:57 ` Gary R Hook [this message]
2016-05-18 16:01 ` Tadeusz Struk
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=573C90E6.8000203@amd.com \
--to=ghook@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=smueller@chronox.de \
--cc=tadeusz.struk@intel.com \
/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.