Hello pardon me for asking newbie question. With the requisite call
mqtt_client_info.tls_config = altcp_tls_create_config_client(cert, sizeof(cert)); Let's say I am using an embedded system with no file system support. I am communicating with a server only and will not be acting as a server for other clients. TLS is used for MQTT data encryption. Is it correct that in this scenario I can use a self-signing certificate? I used Java Keytool to create a .cer file. Is it the case that I can convert the .cer file into a C array, and then use it in the call above? Thanks for any help. On Fri, Aug 3, 2018 at 12:48 AM, [email protected] <[email protected]> wrote: > On 03.08.2018 09:36, Richard Man wrote: > >> Hi Simon or others, I am attempting to build 2.1.0 RC1 with ALTCP, >> specifically with the mbedTLS 2.12.0. Looks like I need to map the function >> pointers in altcp_tcp.h to the mbedTLS functions, but if there is a working >> example that I can leverage, I would appreciate it. There is some urgency >> in this (but why of course). >> > > The altcp functions are mapped to mbedTLS in the files under > "src\apps\altcp_tls\". You just need to enable them and link them in. > > mqtt initialization works much like normal, but you have to assign a > "tls_config" in struct mqtt_connect_client_info_t: > mqtt_client_info.tls_config = altcp_tls_create_config_client(cert, > sizeof(cert)); > > where "cert" is a certificate readable by "mbedtls_x509_crt_parse()" (e.g. > x509). > > Simon > > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users > -- // richard http://imagecraft.com Beyond Arduino - When you're ready to get serious... JumpStart C Tools for Atmel AVR and Cortex-M, The Better Alternative
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
