Thanks for the response Dirk.
I tried, but could not see the certificate public key algorithm - as
x509v3-ssh-rsa or x509v3-rsa2048-sha256.
I use below openssl commands to generate the user certificate:
openssl req -nodes -new -x509 -keyout userkey.pem -out
userreq.pem -days 365 -config
Dear OpenSSL users
Thanks for thinking about it.
(Especially grateful to Mr./Ms. Mattl, Michael and Kris. )
I took a little time to clarify our questions.
The attached document is a diagram of our idea
of how the original protocol and TLS should work together.
Objective:
We want to implement
Thanks for the explanation. I figured I was headed down a dead end. This will
at least help me figure out how to handle things appropriately.
Zeke Evans
On 01/09/2021 16:36, Zeke Evans wrote:
Is there any way to check the status of client authentication sent in a
TLS 1.3 handshake after SSL_connect returns? With TLS 1.2 SSL_connect
seems to always capture the status and return an error code if it failed
but not TLS 1.3. I haven’t been
On Wed, Sep 01, 2021 at 03:36:36PM +, Zeke Evans wrote:
> Hi,
>
> Is there any way to check the status of client authentication sent in a TLS
> 1.3 handshake after SSL_connect returns? With TLS 1.2 SSL_connect seems to
> always capture the status and return an error code if it failed but
Hi,
Is there any way to check the status of client authentication sent in a TLS 1.3
handshake after SSL_connect returns? With TLS 1.2 SSL_connect seems to always
capture the status and return an error code if it failed but not TLS 1.3. I
haven't been able to find a good way to do this after
