I am new to openHAB.I am currently working on MQTT. I need a secure transmition of data so I searched and got a clue on tls on openhab.But unfortunately some link told that openhab MQTT binding does not support TLS.Any idea on this please share me.
This is the link.
http://blog.jensihnow.de/archives/762-How-to-bridge-between-Mosquitto-MQTT-and-AWS-IoT-MQTT-Broker-to-publish-openHAB-Smarthome-data-to-the-Cloud.html
Thank you.
Related
I have a SIM800L module. Which has R14.18 firmware(supports TLS 1.0 and SSL) in it. I am having trouble to connect to http"S" servers. I can connect http servers no problem there. All this information and steps i got from datasheets, forums and YouTube videos. But i havent seen anyone connect to http"S" servers specifically.
I have no idea what I am missing if someone could rightdown the steps as a dummies guide that would be great.
Thanks in advance.
P.S: I am planing to use this with arduino iot cloud api any help would be appreciated there!
So far i tried;
Configuring the bearer and http with AT commands always getting 601,603,605 etc.
I checked the DNS and SSL cert but I'm not confident there since these are new to me
Tried to connect with TCP/IP wasn't able to connect.
Ok i figured it out i just needed to be a bit more careful that was all :)
While connecting to the mqtt server I'm setting useSSL to true.
443 port is being used.
I need to use SSL pinning with this call, is setting useSSL flag enough?
If not then suggest me the way in which I can use SSL pinning to securely connect with the server.
I didn't fine anything related to certificate pinning in the react_native_mqtt library.
Also, one of the libraries suggested to connect using node's tls.connect(). If anyone have used this ever please share.
Thanks
I was also facing the same problem, what I did was I added addition field to connect
client.connect({ onSuccess: onConnect, useSSL: true ,userName:"brokerUsername", password:"brokerPassword" })
and it worked for me.
I am implementing a minimal SUPL 2.0 client. I have added SUPL ASN1 specification and LPP ASN1 specification with my application and compiled it. I am trying to implement a SET initiated Immediate services scenario.
I have filled all the fields to SUPL START message with LPP protocol information and LTE cell id (location id) information. I am sending this message to supl.google.com, but I am not able to receive any response from the google supl server.
Does google supl server support LPP?
I have tried with supl.nokia.com also. Similarly I am not getting any response with nokia supl server also.
The same application code is working fine for RRLP protocol.
Please let me know if anybody has come across the similar issue or have some information regarding LPP protocol usage with google SUPL 2.0 server.
Yes, supl.google.com supports SUPL 2.0 and LPP. What port number are you using for the SUPL connection? I think 7275 is encrypted, 7276 is not. You could implement OpenSSL or other encryption, but I would just use 7276.
Are you setting the LPP capability bit? Are you sure you got all your asn.1 packing and aligning done correctly? RRLP working is a good indicator that you know what you are doing, but I think the usual case for no response is a badly formed message.
I'm struggling with Netty 4.0.8 Websocket client example and SSL and I can't seem to be able to send data to the Netty SSL websocket server example. Although there have been many posts around this issue, (I went through all, I believe), and the most common suggestion is to just add an sslHandler to the beginning of the pipeline, it doesn't work. Handshake seems to be successful as it is also indicated to a relevant question here.
I remember being in the same situation with version 4.0.0, but I somehow managed to get it working. However, things (and API) changed when I upgraded to 4.0.8.
Can the Netty developers add a working Websocket SSL client example to the examples? Many people struggle with this issue and that would be useful. Maybe the solution is just too simple, but an example would clear things. Again, sorry for reposting a question that might be already there, but the relevant question has also been unanswered and my reputation is just too low to add a comment to other relevant questions :)
I seem to have found a solution to my own question. The sample code on the client uses the channel.write() method, which seems not to send the messages to the Websocket ssl server. By using the channel.writeAndFlush() instead, messages are correctly sent to the server.
A Zookeeper architecture question for you ZK Gurus:
I use zookeeper to manage messaging to a cloud of worker machines. Currently the application servers that control the messages and the workers are in the same infrastructure (network). I'm considering allowing clients to communicate with these servers outside of the network from arbitrary locations. I've read about Zookeepers ACL and Authentication Capabilities but I notice that digest sends the passwords in cleartext. I'd be concerned about securing the socket connection and protecting against outside attacks. I dont see anything online telling me that this IS/IS NOT something that can/should be done with Zookeeper.
Is this a common architecture with Zookeeper and are there any suggestions?
Am I barking up the wrong tree for this type of work?
if you do not have a secured network (VPN), this in not something you should do for exactly the reason pointed out. you can mitigate the problem quite a bit using the kerberos plug in, which will secure the authentication and authorization, but you still will not get confidentiality (encryption). what you really need is SSL. things are setup now so that SSL support could be implemented, but code still needs to be written :)