kreationnext

Results 6 comments of kreationnext

Thanks. It works smooth. But TLS1.3 gives me handshake failure. And also there is issue with session ticket[changed the session to null so that I can work with it].

following the issue #317 resolved the session ticket issue. TLS 1.3 still gives Handshake failure

Thank you for the response. > If you still have code doing anything with EllipticCurvesExtension as you described in the first post here, definitely remove it This is already removed...

I am just using the TLS library from org.bouncycastle.tls. It doesn't throw any error that I can stacktrace. This is what I get from wireshark ![image](https://user-images.githubusercontent.com/16913501/135204822-0c404a33-1d8c-433f-87d9-162c4f4bdd21.png) The first Encrypted Alert...

1. Yes I am getting notifyHandshakeComplete. 2. I want to implement h2 protocol not h2c. 3. I am testing the site https://www.google.com and the signatures from https://ezdiscord.xyz/fingerprint. No TLS RENEGOTIATION...

The issue regarding HTTP2 is solved. It was because of the frame contents which were rejected. So now it works good. Thanks your your help and support