News for hackers. Stuff that matters.
Re:I spent a week without IPv4 (2023) by nottorp on Sunday December 21, 2025 @03:57PM (#46348346)
> to exhaustively enumerate every single publicly accessible server on your entire network

Enterprise thinking. It's not the publicly accessible servers i worry about, it's the other boxes that shouldn't be publicly accessible...

Re:I spent a week without IPv4 (2023) by Dagger2 on Monday December 22, 2025 @02:16PM (#46357678)
That's what I meant. On v4, it's trivial to find every server that can be reached from the Internet, whether it was intentional or not. It's not so trivial on v6.
Re:I spent a week without IPv4 (2023) by immibis on Monday December 22, 2025 @04:07PM (#46359097)
Note that V6 is easier to scan than some people assume. You don't have to scan all 2^128 addresses - you can look at provider address blocks in the registry, and make an assumption (or try it and see) what size block that provider assigns to each server, and then guess the server is ::1 or ::2 in each block. This isn't an exhaustive scan, but you'll find a lot of services this way anyway.
Re:I spent a week without IPv4 (2023) by Dagger2 on Tuesday December 23, 2025 @06:29AM (#46364445)
You can also e.g. monitor certificate transparency logs for hostnames. But the difference is that without NAT, knowing about one server on the network doesn't automatically give you the IP for every other accessible server on the same network. You have to actually try host IPs one by one instead of the router kindly filling that part in for you.