3 ms·
Keep that in mind "easily" can be good for you, but not for your users--- https://blogs.msdn.microsoft.com/tonyschr/2004/03/30/drivers-a-new-kind-of-bloat/ htt
by userbinator 8y ago
Keep that in mind "easily" can be good for you, but not for your users---
https://blogs.msdn.microsoft.com/tonyschr/2004/03/30/drivers-a-new-kind-of-bloat/ https://blogs.msdn.microsoft.com/tonyschr/2004/03/30/drivers...
Even if it's just restricted to the local machine, any application that seemingly should have nothing to do with the network is going to arouse plenty of unneeded suspicion if it starts listening on a port or creating connections. Several years ago I remember coming across an application written in Python that did something similar, and its forums had users complaining that their firewall had detected something or that it was otherwise not working. I downloaded the executable, analysed it to discover the above, and decided to find an alternative instead.
- nine_k 8y agoWhy would a firewall care about anything listening on localhost? Why an app exposing itself to a local GUI process would listen on anything but localhost? I wonder if websockets can work on Unix domain sockets; it's the normal way for non-websockets programs of a similar architecture.
- nineteen999 8y agoWell Websockets sit atop HTTP last time I looked, what would be the point of using HTTP over domain sockets? I must be missing something - I thought the main reason so many protocols are implemented atop HTTP these days is because traditionally many corporate firewalls block nearly everything else.
- GauntletWizard 8y agoYou still need the HTML served somewhere - running a HTTP server on domain socket is a reasonable way of serving the that if it's at all dynamic, and since you've already got the socket open why not reuse it and do websocket over it too? Once the socket has transitioned, there's no overhead.
- userbinator 8y agoWhy would a firewall care about anything listening on localhost? Not sure about now but it used to be very common for adware/spyware to setup a local HTTP proxy and reroute all traffic through that. There's also the "why is this app that has nothing to do with the network, doing something with networking?" angle to consider. Some malware would try to hide by injecting itself into other innocuous processes.