News for hackers. Stuff that matters.
Re:Direct Sockets API in Chrome 131 by theamk on Saturday November 02, 2024 @01:11AM (#42024198)
I sure hope not, this will bring in a new era for internet worms.

If some ISPs are not currently firewalling all incoming IPv6 connections, it's a major security risk. I hope some security researcher raises boise about that soon, and the firewalls will go closed by default.

Re:Direct Sockets API in Chrome 131 by 1oooqooq on Saturday November 02, 2024 @01:59AM (#42024329)
it kinda of already begun
Re:Direct Sockets API in Chrome 131 by modeless on Saturday November 02, 2024 @02:19AM (#42024402)
Has there been a big ipv6 worm? I thought that the defense against worms was that scanning the address space was impractical due to the large size.
Re:Direct Sockets API in Chrome 131 by 1oooqooq on Saturday November 02, 2024 @08:41AM (#42026049)
i don't think they scan the entire space. but even before that there were ones abusing bonjour/upnp which is what chrome will bring back with this feature.
Re:Direct Sockets API in Chrome 131 by immibis on Saturday November 02, 2024 @05:47AM (#42025219)
My home router seems to have a stateful firewall and so does my cellphone in tethering mode - I don't know whether that one's implemented on the phone (under my control) or the network.

Firewalling goes back in the control of the user in most cases - the other day we on IRC told someone how to unblock port 80 on their home router.