From: David Howells <dhowells@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: dhowells@redhat.com, Tadeusz Struk <tstruk@gmail.com>,
herbert@gondor.apana.org.au, tadeusz.struk@intel.com,
smueller@chronox.de, linux-api@vger.kernel.org,
marcel@holtmann.org, linux-kernel@vger.kernel.org,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
zohar@linux.vnet.ibm.com,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
peterhuewe@gmx.de
Subject: Re: [PATCH v2] crypto: AF_ALG - add support for keys/asymmetric-type
Date: Wed, 13 Jan 2016 13:36:51 +0000 [thread overview]
Message-ID: <10839.1452692211@warthog.procyon.org.uk> (raw)
In-Reply-To: <1452688062.88154.32.camel@infradead.org>
David Woodhouse <dwmw2@infradead.org> wrote:
> David, is there a way to do that test purely in software without
> needing hardware support? We know that the data might not actually be
> present in all cases... is there an easy test for that case?
I have written a user TPM driver that talks to a userspace TPM implementation
out of the backend. It's been pushed to the TPM driver guy but I'm not sure
what became of it. I'll chase it up.
David
next prev parent reply other threads:[~2016-01-13 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 15:50 Tadeusz Struk
2016-01-12 5:56 ` Tadeusz Struk
2016-01-13 12:27 ` David Woodhouse
2016-01-13 13:52 ` Tadeusz Struk
2016-01-13 13:31 ` David Howells
2016-01-13 14:05 ` Tadeusz Struk
2016-01-13 15:06 ` David Woodhouse
2016-01-13 16:14 ` Tadeusz Struk
2016-01-16 10:51 ` David Howells
2016-01-13 13:36 ` David Howells [this message]
2016-01-13 13:45 ` David Woodhouse
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=10839.1452692211@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=peterhuewe@gmx.de \
--cc=smueller@chronox.de \
--cc=tadeusz.struk@intel.com \
--cc=tstruk@gmail.com \
--cc=zohar@linux.vnet.ibm.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 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®