Hi Michael,
Without doing ssl_accept on the ssl will getpeername work? Also using the
existing ssl with ssl_accept for the first connection we don’t get the
information of second peer. Thus we ended up creating new bio/ssl each time we
get a request.
Any suggestions?
Thanks,
Grace
On 12-Jan
I have problem doing handshake using "ECDHE-ECDSA-AES256-GCM-SHA384"
cipher.
OpenSSL 1.0.2h
This is how I generate test certificates.
openssl ecparam -out /data/ca.key -name secp256k1 -genkey
openssl req -x509 -new -key /data/ca.key -out /data/ca.pem -outform PEM
-days 3650 -subj '/C=SE/ST=S/L=M/O
List spamming? For this one message I think not:
I have professionally benefitted pretty much through the entire history of
OpenSSL and its
predecessors and I strongly 2nd "Google Esatz"'s message.
With sincere thanks to everyone involved in the open source encryption world,
and the
OpenSSl t
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Grace Priscilla Jero
> Sent: Friday, January 12, 2018 07:04
> Whenever a connect is initiated from any client we need to know if it is
> already connected client or a new client.
> We are doing this by
> • creatin
Hi All,
Below is our scenario on DTLS.
We have multiple connections to the same server. We have mapped one fd to
the ssl in the server to receive all connections.
Whenever a connect is initiated from any client we need to know if it is
already connected client or a new client. We are doing this
