Okay, I think I get it. Every OpenSSL example I have seen uses BIO, but
there is no need to use BIO, right (unless one wants I/O-type-independence)?
I have eliminated all of my BIO usage. I'm using normal TCP/IP bind(),
select(), accept(), and then SSL_set_fd(ssl, socket) and SSL_accept(); I
then
You can actually skip the step of using the BN functions and write your keypair
directly to PEM format:
PEM_write_bio_ECPrivateKey
You can then use the BIO functions to either read a string from memory, write
it to file, etc. See: http://www.openssl.org/docs/crypto/bio.html#
Jason
On Aug 15,
Hi,
Based on the previous conversations, I tried to generate Elliptic Curve
public/Private key pair. I want to convert the output BIGNUM* to char* in order
to perform the rest of my task. Using BN_bn2hex is the correct api to do this?
It seems it returns a 32 byte Hex while when I generate EC k
Hi Adrien,
Just out of curiosity, what version of OpenSSL are you using? I can get OCSP
to work with version 0.9.8, but not 1.0 or later and Im looking to see if
anyone else has had any luck with the current version.
Thanks,
Steve
From: owner-openssl-us...@openssl.org
[mailto:owner-op
I'm designing a protocol that requests certificates for specific public
keys known to the client. (I.e., the client says, "give me all of the
certs you know that are for one of these public keys," and the server
responds with those certs.)
In order to keep the request size small, I'd like to incl
