On: The Ripe NCC Has Run Out of IPv4 Addresses

[Dagger2]

No... it doesn't drop connections, so it doesn't provide any security.

[icedchai → Dagger2]

In practical terms, it still provides some (low) level of security. If an attacker can't get IP packets to your machine because it's on an un-routable address, they can't attack it. If your attacker is getting "cooperation" from your ISP to route to it, you have bigger things to worry about it.

Obviously you should really use a firewall...

[Dagger2 → icedchai]

It won't prevent an attacker from getting IP packets to your machine. How could it do that, when it only acts on outbound connections and its only act is to change the apparent source address of those connections?

[icedchai → Dagger2]

Did you miss "because it's on an un-routable address" part? If there's no route to your machine from an attacker, they can't attack you.

[Dagger2 → icedchai]

The discussion was about the behavior of PAT, and PAT has no influence on whether or not an attacker has a route to you.

[icedchai → Dagger2]

The discussion is about NAT and PAT in general. 99% of the time it is used with unrouteable private addresses. This means even in the absence of a firewall there is still some level of security. End of story.

[Dagger2 → icedchai]

It's common to use it with RFC1918 addresses, but that still doesn't change the behavior of PAT. PAT will not drop connections, and thus won't provide you with security.

[icedchai → Dagger2]

Security is not black or white, it is shades of gray. We'll just have to disagree.

[Dagger2 → icedchai]

The behavior of PAT is, though. You can sniff packets and confirm that it behaves the way I'm describing.

[icedchai → Dagger2]

I already know this.