Robert Merget

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.

On which version of TLS-Attacker are you? We recently had bigger changes around this, I want to make sure that the solution will work for you.

I think the issue is that we changed the capiatlisation in newer versions of TLS-Attacker. Try **B**yteArrayExplicit...

Hm, our GOST support is not so good. I had a student implement it for fun, but as we ourselves literally nether use it I don't know if the code...

This is fairly easy, you can just send the Messages in distinct actions, this will also send them in different TCP packets. If you want more complicated mixing it gets...

Splitting across records is also fairly easy, as you can also define the records in the workflow trace. This would look like this: ``` HANDSHAKE 16 HANDSHAKE 32 HANDSHAKE 10000...

Ah i see, i dont think we have a flag or a good interface for that as of yet, but i think it can be easly added. You would need...

With plainRecordBytes you can manually hack this together, but its not really useable. You could theoretically send the same message twice and use a byteArrayDeleteModification to first strip the end...

We decided to put this into TLS-Attacker 4.0, which is a complete rework of the framework to properly implement this feature - will take some more time

Hey, The problem is in the Config object. TLS-Attacker requires you to explicitly set default values for everything such that TLS-Attacker know how it is supposed to send its messages....