Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] paho.mqtt.c library status

Hi there

I am facing the same problem as Sylvain.
Using the paho C client.
No way to get TLS to work. Always getting rc = -1 from MQTTClient_connect().

Also I wonder, whether the TLS version should be settable.

Could anyone help me and say if TLS is really working in the C client?
If yes, could you please give an example for TLS 1.2?
I try to connect to test.mosquitto.org:8883 with the certificate mosquitto.org.crt.

I downloaded the latest sources from https://github.com/eclipse/paho.mqtt.c.git
Compiling on Ubuntu/CLion with -DPAHO_WITH_SSL (the *s libs are built).

I successfully worked with a mosquitto based client, but would prefer the paho implementation.

Thanks and regards

Michael


--
Michael Krebietke | SOTEC | m.krebietke@xxxxxxxx | T +49 7033 5458-37 | F +49 7033 5458-95

2017-02-02 15:00 GMT+01:00 Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx>:

We've just set up a Mattermost (open source Slack clone) channel:

    https://mattermost.eclipse.org/eclipse/channels/paho

not everyone has joined yet.  As far as the C client goes, I am the main developer so far...

Ian


On 02/02/2017 12:41 PM, Otavio Piske wrote:
Ian,

thanks. I have been looking at the Ant file to help me prepare the CMake PRs. I have been trying to keep it somewhat similar to that.

The TLS tests will be a bit more complicated, indeed. I am still exploring what to do in this case. One idea I have in mind for that is to create a separate axis in the CI (matrix) and inject the TLS configuration only on those specific tests. I'd like to provide a way that it's possible to use both the existing configuration (iot.eclipse.org) as well others. I believe the resulting CMake file would be simpler to maintain in this case (since there would be no test orchestration within it).

For the Windows build on AppVeyor, it is currently building w/ Visual Studio 2015. The only difference is that it is currently using nmake instead of Visual Studio solution files to do the build (which uses msbuild, I believe). I also exploring a bit here, but I would like to contribute w/ something that allows it to iterate over different build environments as provided by AppVeyor and that executes the same tests as those in Linux/OS X.

Obs.: is there an IRC channel or similar for Paho development that I should/could join to possibly discuss this and interact more w/ the developers?

Kind regards

On Thu, Feb 2, 2017 at 11:09 AM, Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxx.uk> wrote:

P.S.  I still want to have a Windows build that uses Visual Studio, and runs on AppVeyor running the tests.  I think, although you can say I don't have proof, that Windows users will want to primarily build with the MicroSoft tools.

Ian


On 02/02/2017 09:57 AM, Ian Craggs wrote:

Otavio,

that's really great - that was next on my to do list. 

I was just getting the standard Make working properly on Travis CI.  The base Make is working now, but not the tests, but I can get that working by calling Ant. 

The biggest hurdle is with the TLS tests as I created a special Mosquitto configuration.  The Mosquitto running that config is on iot.eclipse.org, but is not visible outside the eclipse.org domain.  We could run that somewhere else, or open the ports or change the tests/configuration.

Ian

On 02/02/2017 09:31 AM, Otavio Piske wrote:
Hello,

The CMake build does not build the tests, indeed. Since I offered to help w/ the CMake bits on the project, I would like to provide a brief update on that.

I am currently working on a set of PRs for the CMake build so that it builds and runs the tests. I have tied this to a Travis CI job and it currently builds the code and runs the unit tests. At the moment test1, test2, test4 and test6 pass; test3 and test5 fail and test8 and test9 timeout on Linux [1]. I intend to have the same on both OS X (although progress has been slow due to recent instabilities on Travis) as well as Windows (using AppVeyor [2]).

It's on very initial state but if anyone is interested on those CMake patches, the code for that is available on cmake-tests-travis and cmake-tests-appveyor branches on my repository https://github.com/orpiske/paho.mqtt.c.
Kind regards

On Thu, Feb 2, 2017 at 1:15 AM, Guilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com> wrote:
Hello Sylvain,

2017-01-30 7:14 GMT-06:00 Sylvain Miermont <sylvain.miermont@xxxxxxxxx>:
> 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.
>

With the Autotools build you can use:

$ make check

However, as far as I know, the current CMake scripts do not build the
test directory.

Best regards,

--
Guilherme Maciel Ferreira
Site: http://guilhermemacielferreira.com/
Skype: guilherme.maciel.ferreira
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev



--
Otavio R. Piske
Messaging Quality Assurance Engineer


_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev
-- 
Ian Craggs                          
icraggs@xxxxxxxxxx                 IBM United Kingdom
Eclipse Paho Project Lead; Committer on Eclipse Mosquitto;
Tech Lead in IBM Watson IoT Platform

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev
-- 
Ian Craggs                          
icraggs@xxxxxxxxxx                 IBM United Kingdom
Eclipse Paho Project Lead; Committer on Eclipse Mosquitto;
Tech Lead in IBM Watson IoT Platform

_______________________________________________ paho-dev mailing list paho-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/paho-dev
--
Otavio R. Piske Messaging Quality Assurance Engineer
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev
-- 
Ian Craggs                          
icraggs@xxxxxxxxxx                 IBM United Kingdom
Eclipse Paho Project Lead; Committer on Eclipse Mosquitto;
Tech Lead in IBM Watson IoT Platform


_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev


Besuchen Sie unseren Chrome Webshop unter shop.cloudwuerdig.com

www.sotec.eu | www.cloudwuerdig.com 
-- 
SOTEC Software Entwicklungs GmbH + Co Mikrocomputertechnik KG 
Calwer Straße 11, D-75395 Ostelsheim 
Sitz Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664, Geschäftsführer: Florian Holz 
Cloudwürdig® ist eine eingetragene Marke der SOTEC Software Entwicklungs GmbH + Co Mikrocomputertechnik KG

Der Inhalt dieser e-Mail ist ausschließlich für den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser e-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser e-Mail unzulässig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der e-Mail in Verbindung zu setzen.

The content of this e-mail is meant exclusively for the person to whom it is addressed. If you are not the person to whom this e-mail is addressed or his/her representative, please be informed, that any form of knowledge, publication, duplication or distribution of the content of this e-mail is inadmissible. We ask you, therefore, in such a case to please contact the sender of this e-mail.


Back to the top