TLS 1.2 HandShakeFailed / spurious handshake after sending client certificate

[lovehermadly]

No description provided.

[lovehermadly]

When trying to use warp-tls with a self-signed X509v3 certificate having key usages digitalSignature and keyEnciperherment set and being signed with RSA and SHA256 hashing, the TLS 1.2 handhake aborts with a "spurious handshake" message after a fatal alert InternalError.

My warp-tls instance is configured with tlsWantClientCert = True and with a onClientCertificate Serverhook which always returns CertificateUsageAccept for testing purposes.

The same issue can be reproduces with several recent browsers, e.g. Firefox Quantum 64 Bits on Ubuntu 18.04.

BTW, warp-tls currently does not support configuration of a CA certificate for providing it to the client during the certificate request message as a typical client certificate selection criterion.

[ocheron]

Yes, same with tls-1.4.1 and current master.
The state machine used by the server fails when ClientKeyXchg and CertVerify are in the same packet.
I'll send a patch soon.

[kazu-yamamoto]

BTW, warp-tls currently does not support configuration of a CA certificate for providing it to the client during the certificate request message as a typical client certificate selection criterion.

Would you bring this to https://github.com/yesodweb/wai?