Hello Ian
Thank you for your answer, I understand maintaining a
complex build system takes time.
There were targets in the deprecated Makefile to build test
files and specifically stuff in 'test/ssl'. Using the new
build system, I didn't find ways to build those examples.
This would be helpful for SSL troubleshooting.
Just a quick question, in case there is an obvious
answer: I have a program that work ok with the library and
no SSL.
When I configure SSL, MQTTAsync_connect always returns -1.
I have:
- checked server conf using another client, with the exact
same certs/keys, and it worked
- configured the server to be as lax as possible without
disabling SSL
- tested with and without client certificates in the
library configuration
- checked cert/key permissions and contents
I have digged a little bit in the sources, and
MQTTAsync_connect should typically return some kind a
meaningful error code. What is the subsequent call that fail
and could explain this -1 code?
Could it be an issue with SHA2 certs, or 4096b RSA keys?
I'm assuming the mqtt library is forwarding all SSL
parameters to OpenSSL and letting it do its magic, maybe I'm
wrong.
Regards,