echo_server example fails to build for ESP32 due to redefinition of certs #826

Activity

1. embhorn

   assigned

   gojimmypi

   on Aug 21, 2025
2. embhorn commented on Aug 21, 2025

   

   embhorn

   on Aug 21, 2025

   Member

   More actions

   Hello @fastjack ,

   Thanks for contacting wolfSSL Support. I have requested a review of this issue by our engineers. Could you tell us a bit about your ESP32 project using wolfSSL?

   Thanks,
   @embhorn - wolfSSL Support
3. gojimmypi commented on Aug 21, 2025

   

   gojimmypi

   on Aug 21, 2025

   Last edited by gojimmypi

   Contributor

   More actions

   Hi @fastjack and @embhorn

   I've confirmed this is problematic with multiple versions of the ESP-IDF. I tested on latest master ESP-IDF v6.0

   The root cause appears to be specific the the most recent v5.8.2 Managed Component release of wolfSSL which was not tested against the prior published wolfSSH examples.

   Specifically, the same-name certs_test.h file is included in both wolfSSL and wolfSSH components,

   ... but gated with #define WOLFSSL_CERTS_TEST_H (SSL) and #define _WOLFSSH_CERTS_TEST_H_ (SSH), respectfully.

   As an interim fix until I resolve this, one can set an explicit version of wolfSSL in the wolfssh_echoserver/main/idf_component.yml:

   dependencies:
     idf:
       version: '>=4.1.0'
     wolfssl/wolfssh:
       version: ^1.4.20
     wolfssl/wolfssl:
       version: 5.8.0

   Note the last line was changed from the default:

       version: ^5.7.6
   

   to

       version: 5.8.0
   

   ... to use the prior release from current wolfssl v5.8.2. Be sure to OMIT the "greater than version" carat: ^ char.

   Be sure to fully clean the prior build from the wolfssh_echoserver directory:

   rm -rf ./build
   rm ./dependencies.lock

   See also: wolfSSL/wolfssl#9099 that changed sizeof definitions to macros after the v5.8.2 release.
4. gojimmypi commented on Aug 21, 2025

   

   gojimmypi

   on Aug 21, 2025

   Contributor

   More actions

   Update: the root cause of this problem is from wolfSSL/wolfssl#8813, specifically line 1084 of the template example user_settings.h.

   The reminder in comments to #include <wolfssl/certs_test.h> was uncommented, thus causing conflicts between the certs_test.h in wolfSSL and the same-name file in wolfSSH.

   An alternative solution to this problem would be to simply edit the respective user settings file in:

   wolfssh_echoserver/managed_components/wolfssl__wolfssl/include/user_settings.h
   

   and comment out the #include <wolfssl/certs_test.h> line.

   Of course, in doing so, one would also need to then convert the entire component to a non-managed one as prompted.

   $ idf.py fullclean
   Executing action: fullclean
   Executing action: remove_managed_components
   ERROR: Some components in the "managed_components" directory were modified on the disk since the last run of the CMake.
   
   wolfssl__wolfssl: Hash of the file "include/user_settings.h" in the component in "/mnt/c/test/wolfssh_echoserver.bak/managed_components/wolfssl__wolfssl" does not match expected hash "8ac1b765e20c9034f36bef312cb7a97589b6fb4d2582f7be68d52662498a171a"
   
   Content of this directory is managed automatically.
   If you want to keep the changes, you can move the directory with the component to the "components" folder of your project.
   I.E. for "wolfssl__wolfssl" run:
   mv /mnt/c/test/wolfssh_echoserver.bak/managed_components/wolfssl__wolfssl /mnt/c/test/wolfssh_echoserver.bak/components/wolfssl__wolfssl
   If you want to discard the changes, remove the whole component directory from the "managed_components".
   

   A post-release wolfSSL Managed Component will be needed - as once published, version numbers cannot be reused.
5. gojimmypi commented on Aug 24, 2025

   

   gojimmypi

   on Aug 24, 2025

   Contributor

   More actions

   Hi @fastjack -

   I've published a minor revision 5.8.2~1 of wolfssl in the ESP Registry that uses the current minor change in wolfSSL/wolfssl#9123 to comment out the #include <wolfssl/certs_test.h>.

   No other changes were made to wolfSSL core library. This is still based on the 5.8.2 release; none of the other post release changes were added.

   I've confirmed the wolfSSH idf.py create-project-from-example "wolfssl/wolfssh=1.4.20:wolfssh_echoserver" now works properly, albeit with a few warnings in ESP-IDF v6.0 about newly deprecated SNTP functions.
6. fastjack commented on Aug 24, 2025

   

   fastjack

   on Aug 24, 2025

   Author

   More actions

   I was able to create a new project and build it successfully. The example works as advertised. Thank you!
7. gojimmypi commented on Aug 24, 2025

   

   gojimmypi

   on Aug 24, 2025

   Contributor

   More actions

   Hi @fastjack - thanks for confirming the update works for you.

   If you are interested in another wolfSSH example for Espressif devices, check out the SSH to UART example:

   https://github.com/wolfSSL/wolfssh-examples/tree/main/Espressif/ESP32/ESP32-SSH-Server

   Let me know if there's anything I can do to help you with your project.
8. embhorn

   closed this as completedon Aug 29, 2025