News for hackers. Stuff that matters.

A comment on Node-Red – Flow-Based Programming for the Internet of Things. Parent comment

Re:Node-Red – Flow-Based Programming for the Internet of Things by avian on Tuesday January 08, 2019 @04:09PM (#18859723)
I didn't have any contact with the maintainers, but I found node-RED pretty reliable. It was nice to work with, even though I'm not a big fan of Javascript and Node ecosystems. The third-party blocks from their web library did tend to be pretty buggy in my experience. I tried to stay away from them and (re-)implement my own blocks where I needed them.

Perhaps the worst offense was the insecure-by-default config I mentioned in the other comment. I was unknowingly running it on a public port on a dev machine without auth for months before I realized (the network I was on didn't happen to filter inbound connections on ports >1024).

I used Node-RED pretty extensively for controlling experiments (see e.g. https://github.com/avian2/sigfox-toolbox)

[ Parent | on HN ]
Re:Node-Red – Flow-Based Programming for the Internet of Things by crankylinuxuser on Tuesday January 08, 2019 @05:50PM (#18860565)
Yep. This is probably the only egregious default. And that's horrible.

It should, like any other Linux server, be available via ::1 and 127.0.0.1 without credentials. Better yet would be to automatically run a credential script on install to bootstrap, as this project focuses on ease of use of node.js and modules.

I had my own bugs as well that I reported, to no avail. I did find solutions myself.

[ Parent | on HN ]
Re:Node-Red – Flow-Based Programming for the Internet of Things by knolleary on Tuesday January 08, 2019 @06:27PM (#18860827)
Hi - would like to hear what bugs you reported to no avail. There may well have been good reason they weren't addressed to your satisfaction - or we may have simple not fully appreciated what you were reporting.
[ Parent | on HN ]
Re:Node-Red – Flow-Based Programming for the Internet of Things by crankylinuxuser on Tuesday January 08, 2019 @06:38PM (#18860893)
Indeed. My bug was that setting/changing a proxy required restarting the service, something the service itself could not complete. I needed this to establish connections to Tor hidden services.

Instead, I fixed this via the DNS resolver daemon within Linux itself, so my systems natively can handle .onion sites. In a way, it was a better fix, since every program is torified if connecting to an .onion .

[ Parent | on HN ]