Jens,
"And no binary versions of Paho will be distributed which
have this feature enabled."
I'd like to clarify what this means. We have two versions of the
client library, one with no TLS capability, which does not link to
OpenSSL and will work without it. Conditional compilation of the
code is used to exclude the TLS calls where desired.
The other, TLS enabled version, links to OpenSSL, and OpenSSL is
required on the machine for that version to run. Does this mean
that we could not ship that binary? There are a couple of other
existing approved CQs relating to OpenSSL, which are also
works-with:
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=8766 (Eclipse Titan)
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=1706 (Eclipse
Subversive)
for which I'm guessing that restriction (if I understood correctly)
doesn't apply.
Thanks
Ian
On 04/08/2016 08:09 AM, Jens Reimann
wrote:
Paho requests the use of OpenSSL [1].
Paho will only compile in this feature if it is available on the target
machine. Normal functionality of Paho (without TLS/SSL encryption) is
supported even without OpenSSL. The source code of OpenSSL will not be
checked in. And no binary versions of Paho will be distributed which
have this feature enabled.
+1 from me for works-with
Jens
[1] http://dev.eclipse.org/ipzilla/show_bug.cgi?id=10814
_______________________________________________
iot-pmc mailing list
iot-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-pmc
--
Ian Craggs
icraggs@xxxxxxxxxx IBM United Kingdom
Paho Project Lead; Committer on Mosquitto
|