You would need to publish your code that somebody can debug it.GreetingsBernd-- http://bernd.eckenfels.net
Von: Filip Petr. Gesendet: Freitag, September 1, 2023 6:02 PMAn: security-dev@openjdk.org ; e...@zusammenkunft.net Betreff: Re: Modification of Client
This extension is my custom. It's the same extension that Google chrome
added (https://datatracker.ietf.org/doc/html/rfc8701). You can check this
extension on your Chrome browser using this following URL
https://tls.peet.ws/api/tls
I don't understand why this is an issue for my Java program? I che
rnd-- http://bernd.eckenfels.net
Von: Filip Petr. Gesendet: Freitag, September 1, 2023 10:42 AMAn: security-dev@openjdk.org ; e...@zusammenkunft.net Betreff: Re: Modification of Client hello TLS packet The alerts I'm getting are coming from some random web server i'm hitting
Von: Filip Petr. Gesendet: Freitag, September 1, 2023 10:42 AMAn: security-dev@openjdk.org ; e...@zusammenkunft.net Betreff: Re: Modification of Client hello TLS packet The alerts I'm getting are coming from some random web server i'm hitting and i dont know its architecture. In
The alerts I'm getting are coming from some random web server i'm hitting
and i dont know its architecture. In this error traces I'm submitting it's
www.google.com but it happens for every other domain I'm trying to hit. It
seems that my java app and my client side program is glitching as it's
spot
Hello,Can you confirm, you say the alert is coming from a non-java server, or are you saying your modified handshake is rejected by a Java server? (Or do you think the alert is not received?).I would turn on ssl debug logging and upload the traces to a gist sharing side so
Hiya,
On 31/08/2023 15:00, Filip Petr. wrote:
My goal is for a community of automation experts to have a perfectly
matched Client hello (JA3 hash) fingerprint as modern commercial browsers
so they can do their job more successfully. For this to happen one must add
8 additional extensions to the
