Hi Matt,
Thanks so much for your response. Now I see what the 'tbs' acronym
is for!
I do have another question: this regards setting the signature in
the signature element of the request. I figured out how to make an
ECDSA_SIG object using the r and s components of the ECDSA
On 29/04/2021 15:04, Joe Eremita wrote:
datasig_len = i2d_X509_REQ_INFO( req->req_info, NULL );
You can achieve this by instead doing:
datasig_len = i2d_re_X509_REQ_tbs(req, NULL);
See:
https://www.openssl.org/docs/man1.1.1/man3/i2d_re_X509_REQ_tbs.html
Matt
Hello all,
I am developing a library that uses an HSM, and I need to create a CSR
to send to the CA. I have some examples using the X509_REQ to set the
public key and attributes. I 've also seen examples of signing the CSR,
which finds the req_info that is needed to sign the CSR:
Hi All,
We have crypto engines for offloading operations like RSA, digests and
ciphers, hmac etc. We are looking at a way to load and unload engines at
run time. This is needed as we need to use the engine when needed for
crypto operations. Else we plan to use openssl for the same.
We tried,
->
The 'fips' option is now disabled by default.
For the 'makedepend' option, several people raised concerns whether the
disadvantages of disabling it
wouldn't outweigh the performance gain at build time, see discussion in pull
request #15050.
So I decided to drop pull request, the 'makedepend'
Hi,
On 28/04/21 21:22, Robert Smith wrote:
Hi Jan,
Thank you for your response.
Obviously the file mem_dbg is not included and that is why I am having
this problem.
The questions are:
Whether the "enable-crypto-mdebug" flag supported in Windows at all?
Whether this is known issue?
What
