feat(mqtt): enable custom TLS cipher suites for MQTTs (IDFGH-15198) #298
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
ciphersuites_list
toesp_mqtt_client_config_t
for specifying TLS cipher suites.This change allows users to flexibly select the TLS cipher suites used in MQTT communication, improving the ability to meet increasingly stringent network security certifications. By adding the
ciphersuites_list
toesp_mqtt_client_config_t
, users now have full control over the encryption suites used in the connection, which enhances security and adaptability in various environments.The provided cipher suite list is not copied or freed by the client, so users are responsible for managing the memory of the list.
Related
Dependent on this submitted change
espressif/esp-idf#15868
Testing
Tested by configuring the specified TLS cipher suites in the MQTT client configuration and using Wireshark to capture the packets during the TLS handshake. The captured packets were analyzed to verify that the selected cipher suites were indeed used in the communication. This method confirmed the configuration's effectiveness on ESP32-S3 with a secure MQTT broker.