}
return def_meth->rsa_priv_dec(flen, from, to, rsa, padding);
}
==
But this code worked for 1.0.* branch
вт, 19 марта 2019 г., 19:52 Fuchs, Andreas
mailto:andreas.fu...@sit.fraunhofer.de>>:
Following scenario:
I have an engine that implements e.g. RSA decryption.
That eng
Following scenario:
I have an engine that implements e.g. RSA decryption.
That engine links against a library that links against libcrypto to perform RSA
decryption.
Now if I have an application that sets the default library to be my engine,
won't I end up in an infinite loop ?
Or the other wa
, 12:36 PM, "openssl-users on behalf of Fuchs, Andreas"
wrote:
The problem is as follows:
The digest parameter of the TPM2_Sign command is checked against the hash
algorithms supported by the TPM.
If the TPM only supports SHA256, then the maximum size for the digest
parameter
one have any hints please ?
From: William Roberts [bill.c.robe...@gmail.com]
Sent: Friday, November 30, 2018 15:55
To: openssl-users@openssl.org
Cc: Fuchs, Andreas
Subject: Re: [openssl-users] Question on implementing the ameth ctrl
ASN1_PKEY_CTRL_DEFAULT_MD_NID
On Wed
Hi all,
I'm currently implementing a TPM2 engine for OpenSSL over at
https://github.com/tpm2-software/tpm2-tss-engine
The problem I'm facing is that OpenSSL's TLS negotiation will request ECDSA
from my engine with any hash alg, even though the TPM's keys are restricted to
just one specific hash
