> Really, how? By pull request, you mean one against the openssl github
> account so people subscribing to that account see it, I presume? For that to
> happen, the tree the patch is against must actually exist within the account,
> which this one doesn't.
You clone the openssl git repo, create
> Um, that's not really possible given that openssl_tpm_engine is a
> sourceforge project.
Sure it is. You just find it easier to email patches. This is now the second
time you’ve been asked.
And also, you had concerns about the CLA before. Have they been resolved? If
not you should
On Mon, 2017-01-02 at 17:53 +, Salz, Rich wrote:
> > Um, that's not really possible given that openssl_tpm_engine is a
> > sourceforge project.
>
> Sure it is.
Really, how? By pull request, you mean one against the openssl github
account so people subscribing to that account see it, I
On Sat, Dec 31, 2016 at 02:52:43PM -0800, James Bottomley wrote:
> This patch adds RSA signing for TPM2 keys. There's a limitation to the
> way TPM2 does signing: it must recognise the OID for the signature.
> That fails for the MD5-SHA1 signatures of the TLS/SSL certificate
> verification
On Mon, 2017-01-02 at 17:38 +0100, Kurt Roeckx wrote:
> On Sat, Dec 31, 2016 at 02:52:43PM -0800, James Bottomley wrote:
> > This patch adds RSA signing for TPM2 keys. There's a limitation to
> > the way TPM2 does signing: it must recognise the OID for the
> > signature. That fails for the
On Mon, Jan 02, 2017 at 08:50:24AM -0800, James Bottomley wrote:
> On Mon, 2017-01-02 at 17:38 +0100, Kurt Roeckx wrote:
> > On Sat, Dec 31, 2016 at 02:52:43PM -0800, James Bottomley wrote:
> > > This patch adds RSA signing for TPM2 keys. There's a limitation to
> > > the way TPM2 does signing:
