3 ms·
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 crede
by crankylinuxuser 8y ago
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.
- knolleary 8y agoHi - 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.
- crankylinuxuser 8y agoIndeed. 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 .