Not able to build MS-MICE connection after updating OpenSSL

Question

A device that is able to build up a Miracast-MICE connection to Windows with OpenSSL 3.1.4 is not able to do so anymore after updating OpenSSL to 3.3.1 and above (tested with 3.3.1 and 3.4.0 with the same results).

The transactions have been analyzed with Wireshark, and the first packets (Client Hello) seem to work as expected. The only difference we could spot is that at the end of the transactions, a "New Session Ticket, Change Cipher Spec, Encrypted Handshake Message" has a single "Record Layer" section with OpenSSL 3.1.4, whereas two "Record Layer" sections appear with 3.3.1 and 3.4.0. The case with a single "Record Layer" leads to a successful connection and an MS-MICE [PSH, ACK] packet. In the case of two "Record Layer" sections, the other device immediately closes the connection.

There have been some other issues with the MS-MICE handshake in the past like the following one:
https://learn.microsoft.com/en-us/answers/questions/1113835/ms-mice-dtls-handshake-fails-after-flight-4
But we already use SSL_VERIFY_NONE, and as I said, the only thing that has changed is the OpenSSL update. A downgrade makes things work again as expected. Is there any known issue with newer OpenSSL versions or any kind of required adjustment to make MS-MICE work again with them?
Thanks and best regards.

Answer 1

Hello

Thank you for posting in Q&A forum.

Here are a few steps you can take to troubleshoot:

1. Ensure that MS-MICE is compatible with OpenSSL 3.3.1. Sometimes, newer versions of libraries introduce changes that may not be fully compatible with existing applications.
2. If the issue persists, consider reverting to the previous version of OpenSSL (3.1.4) that was working correctly. This can be a temporary solution while you investigate further.
3. Ensure that all configuration files related to OpenSSL and MS-MICE are updated to reflect any changes in the new version. This includes paths, environment variables, and any specific settings required by OpenSSL 3.3.1.
4. Review the logs for both OpenSSL and MS-MICE to identify any specific error messages or warnings that can provide more insight into the issue.

References:

[OpenSSL] update to <3.3.1> · Issue #39142 · microsoft/vcpkg

openssl 3.3.1 test/asn1_time_test.c fails in MSYS on Windows 10

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

Best Regards,

Daisy Zhou

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.