News for hackers. Stuff that matters.
Re:In protest of the web{*} bulldozer, a response to websock... by tzs on Thursday May 21, 2020 @12:33AM (#23254825)
I don't understand the point of blocking all of 192.168/16, 172.16/12, and 10/8. If the point is to block access to other hosts on your LAN shouldn't it just block the one your LAN actually uses?
Re:In protest of the web{*} bulldozer, a response to websock... by pdonis on Thursday May 21, 2020 @11:54AM (#23259958)
I don't understand the point of not blocking all of those ranges. Why should the browser bother trying to figure out which ones are actually used on a particular LAN? All of those IP ranges are designated as private, and that in itself should be reason enough for browsers to block websocket connections to them.
Re:In protest of the web{*} bulldozer, a response to websock... by pferde on Thursday May 21, 2020 @04:10AM (#23255952)
What if the my network uses several different local subnets? How would the browser figure that out?

No, blocking all these IP ranges is a good idea. After all, these ranges are supposed to not be directly routeable to from the Internet.

Re:In protest of the web{*} bulldozer, a response to websock... by tzs on Thursday May 21, 2020 @07:25AM (#23257110)
> What if the my network uses several different local subnets? How would the browser figure that out?

It would look at your computer's routing table. If it is an IP address your computer talks to directly, it is on a LAN your computer is on and would be blocked. If it is an IP address that your computer talks to through a gateway, it is on the internet and would not be blocked.

> After all, these ranges are supposed to not be directly routeable to from the Internet.

They are supposed to not be directly routeable to/from the public internet. They can be directly routable between non-public parts of the internet.

A not uncommon example, especially now, is having a VPN connection between a home network and the internal network of a business, both of which are using addresses in the private ranges.

Re:In protest of the web{*} bulldozer, a response to websock... by pferde on Thursday May 21, 2020 @01:55PM (#23262073)
> They are supposed to not be directly routeable to/from the public internet. They can be directly routable between non-public parts of the internet.

Sure, but this is different from a VPN. This would be untrusted code downloaded from a remote website talking to unrelated devices on my local network. Effectively, it would be the remote website having free reign inside my local network, with my web browser acting as a proxy (or as a trojan horse, with a bit of exaggeration).

Re:In protest of the web{*} bulldozer, a response to websock... by pdonis on Thursday May 21, 2020 @11:55AM (#23259980)
> If it is an IP address that your computer talks to through a gateway, it is on the internet and would not be blocked.

No, this would just make the security problem worse, because now any website could use websockets to scan, not just your personal LAN, but any network you are connected to through a VPN or any other gateway.

Re:In protest of the web{*} bulldozer, a response to websock... by magicalhippo on Thursday May 21, 2020 @08:11AM (#23257442)
I use both 192.168/16 and 10/8 on my computer. One is for my regular LAN and the other is for my 10G link to my NAS.