That means I can clean up the Java Client's Unit Tests as well now, thanks!
Kind regards,
James Sutton Software Engineer - IoT Foundation - MQTT Open Source Projects Technical Trojan - Wimbledon Project |
|
| Hursley Park Hursley, SO212JN United Kingdom |
IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
----- Original message -----
From: Benjamin Cabé <benjamin@xxxxxxxxxxx>
Sent by: paho-dev-bounces@xxxxxxxxxxx
To: development discussions for the mosquitto project <mosquitto-dev@xxxxxxxxxxx>, development discussions for paho project <paho-dev@xxxxxxxxxxx>
Cc:
Subject: [paho-dev] Updated certificate for MQTT sandbox, and secured websockets now enabled
Date: Thu, Mar 17, 2016 2:29 PM
The iot.eclipse.org Mosquitto sandbox is now using a Let’s Encrypt self-signed certificate as opposed to the self-signed certificate it used to. It means that you don’t need to download the server’s public key anymore.
What’s more, secured WebSockets have been enabled as well, so you can use wss://iot.eclipse.org:443/ws in your web applications (and you won’t be basically stuck anymore when trying to do MQTT over WebSockets "unsecured" from an https-served webpage).
Thanks a lot to Sandro Kock for the help in setting this up today, live from the Eclipse Foundation booth at CeBIT ;-)
Benjamin –
Benjamin Cabé – IoT Evangelist
Eclipse Foundation
+33 (0) 619196101
@kartben
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
_______________________________________________
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