TLS-Attacker is a Java-based framework for analyzing TLS libraries. It can be used to manually test TLS clients and servers or as as a software library for more advanced tools.
My TLS-Attacker version is 5.1.6. I use TLS-Attacker as a client to connect to an openssl server whose version is openssl1.0.1f. I modify the WorkflowTrace according to [https://web-in-security.blogspot.com/2019/03/playing-with-tls-attacker.html]() and the concrete xml file (trace.xml) is shown below.
I use openssl to set up TLS service, and then I run TLS-Attacker as a client. The expected result shown in the blog is like this
But I haven't got the same consequence.
The server:
The client:
So I want to ask for help about the reason and what I should yo do .Thank you!
You are sending a ServerHello message not a ClientHello message, this is why the server is (rightfully) complaining. ClientHello and ServerHello are two different messages in TLS.
My TLS-Attacker version is 5.1.6. I use TLS-Attacker as a client to connect to an openssl server whose version is openssl1.0.1f. I modify the WorkflowTrace according to [https://web-in-security.blogspot.com/2019/03/playing-with-tls-attacker.html]() and the concrete xml file (trace.xml) is shown below.
I use openssl to set up TLS service, and then I run TLS-Attacker as a client. The expected result shown in the blog is like this But I haven't got the same consequence. The server: The client: So I want to ask for help about the reason and what I should yo do .Thank you!