News for hackers. Stuff that matters.
Re:The IPv6 Transition by eptcyka on Monday October 21, 2024 @03:27AM (#41901569)
With how trivial generating new addresses in IPv6 is, it'd be cool to have a host block all incoming traffic on its own and have each service that deserves to be reached over the listen on an address unique to the service.
Re:The IPv6 Transition by nlitened on Monday October 21, 2024 @03:56AM (#41901733)
> have each service that deserves to be reached over the listen on an address unique to the service

It’s already a thing. These unique per-service addresses are called “ports” in IP protocol.

Re:The IPv6 Transition by eptcyka on Monday October 21, 2024 @06:47AM (#41902735)
Hosting service A shouldn't mean that every user of service A can also figure out you host C, B and D.

Also, the IP protocol does not care about ports at all. Ports are a thing for UDP and TCP.

Re:The IPv6 Transition by nlitened on Monday October 21, 2024 @10:48AM (#41904782)
> Also, the IP protocol does not care about ports at all. Ports are a thing for UDP and TCP.

You're right, they are one level above.

> Hosting service A shouldn't mean that every user of service A can also figure out you host C, B and D.

It how are ports on a single IP address essentially different from multiple IP addresses within a subnet?

Re:The IPv6 Transition by eptcyka on Monday October 21, 2024 @04:46PM (#41908368)
In a /64, enumerating all hosts will not be as practical as enumerating all ports on a single IP. Further, you will not be able to link that two services are running on the same host by just the IP.