Issue with Handling Invalid or Malformed TLS/DTLS Handshake Messages

[hamma96]

I am working with a TLS/DTLS library and need to handle various scenarios involving invalid or malformed handshake messages. Specifically, I am interested in support for the following:

1. Invalid Handshake Messages
2. Malformed Handshake Messages
3. Unrecognized Extensions

I would like to understand if the library or framework supports these scenarios, or if there are plans to support them. Handling these scenarios is crucial for robust security testing and debugging.

Example Scenario:

For context, here’s a simplified example of how these scenarios might occur:

Invalid Handshake Message: A client sends a handshake message with an incorrect format or unsupported protocol version.
Malformed Handshake Message: A server receives a handshake message with corrupted data.
Unrecognized Extension: A client includes a custom extension in the handshake message that the server does not recognize or support.

If there are existing solutions, workarounds, or updates planned for handling these scenarios, I would appreciate any relevant information or resources.

Thank you for your assistance!