tcp node troubles

[Artem Pastukhov]

Hi all, i am unable to reproduce wit flow this:

echo "HTTP/1.0 200 OK\r\n\r\n" | netcat -l 8080

 Can anyone advice?

[Julian Knight]

Can you describe what you are trying to achieve?

[Artem Pastukhov]

I have a Node-RED installation that is password protected and crypted with ssl cert signed with cacert.org

I'm trying to interact with ifttt.com(get an event from), and it doesn't accept cacert.org cert as valid. So i want to make some flow that listen on another tcp port, kind of simple web server.



среда, 1 июля 2015 г., 23:45:31 UTC+3 пользователь Artem Pastukhov написал:

[Dave C-J]

This sort of works at the most basic level - but it would seem others also have problems with IFTTT and cacert.org

[{"id":"4f13439e.b0ecbc","type":"tcp in","name":"","server":"server","host":"","port":"8080","datamode":"stream","datatype":"utf8","newline":"\\n","topic":"","base64":false,"x":185,"y":442,"z":"ef78dde5.10872","wires":[["e2fe9821.1d0168"]]},{"id":"5c32a275.a3cd5c","type":"tcp out","host":"","port":"","beserver":"reply","base64":false,"end":false,"name":"","x":561,"y":442,"z":"ef78dde5.10872","wires":[]},{"id":"e2fe9821.1d0168","type":"function","name":"","func":"var m = {payload:msg.payload};\nmsg.payload = \"HTTP/1.1 200 OK\\r\\nContent-Type: text/plain\\r\\nContent-Length: 3\\r\\nConnection: close\\r\\n\\r\\nOK.\";\nreturn [msg,m];","outputs":"2","noerr":0,"x":378,"y":469,"z":"ef78dde5.10872","wires":[["5c32a275.a3cd5c"],["8df2512d.720db"]]},{"id":"8df2512d.720db","type":"debug","name":"","active":true,"console":"false","complete":"false","x":571,"y":499,"z":"ef78dde5.10872","wires":[]}]

[Giovanni Angoli]

Dave, I've came to the same conclusion yesterday. (cacert.org ssl certificate + IFTTT = no go).  I've deleted the test IFTT recipes that I was trying but basically the message reported in the recipe logs was something like:

action skipped because there's a self signed certificate in the chain. 

That's because cacert.org root CA certificate is non included in the "default" certificate store. (not in the browser, nor system wide linux store)

An alternative could be startSSL free class 1 certificates. Their CA certificate (starcom) is included, as far as I know.

On Fri, Jul 3, 2015 at 9:58 AM, Dave C-J <dce...@gmail.com> wrote:

This sort of works at the most basic level - but it would seem others also have problems with IFTTT and cacert.org

[{"id":"4f13439e.b0ecbc","type":"tcp in","name":"","server":"server","host":"","port":"8080","datamode":"stream","datatype":"utf8","newline":"\\n","topic":"","base64":false,"x":185,"y":442,"z":"ef78dde5.10872","wires":[["e2fe9821.1d0168"]]},{"id":"5c32a275.a3cd5c","type":"tcp out","host":"","port":"","beserver":"reply","base64":false,"end":false,"name":"","x":561,"y":442,"z":"ef78dde5.10872","wires":[]},{"id":"e2fe9821.1d0168","type":"function","name":"","func":"var m = {payload:msg.payload};\nmsg.payload = \"HTTP/1.1 200 OK\\r\\nContent-Type: text/plain\\r\\nContent-Length: 3\\r\\nConnection: close\\r\\n\\r\\nOK.\";\nreturn [msg,m];","outputs":"2","noerr":0,"x":378,"y":469,"z":"ef78dde5.10872","wires":[["5c32a275.a3cd5c"],["8df2512d.720db"]]},{"id":"8df2512d.720db","type":"debug","name":"","active":true,"console":"false","complete":"false","x":571,"y":499,"z":"ef78dde5.10872","wires":[]}]

--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Giovanni Angoli

[Artem Pastukhov]

Thanks, this is exactly what i need!

пятница, 3 июля 2015 г., 11:11:26 UTC+3 пользователь Giovanni Angoli написал:

[Julian Knight]

Agree that startSSL is better in this case. Certificate based authentication is a tricky old area. Great when properly configured but a pain to get their and to keep it there.