Re:The Ripe NCC Has Run Out of IPv4 Addresses
by Dagger2 on Thursday November 28, 2019 @10:22AM
(#21657898)
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?
[ Parent
| on HN ]
Re:The Ripe NCC Has Run Out of IPv4 Addresses
by icedchai on Thursday November 28, 2019 @11:07AM
(#21658261)
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.
Re:The Ripe NCC Has Run Out of IPv4 Addresses
by Dagger2 on Thursday November 28, 2019 @02:02PM
(#21659500)
The discussion was about the behavior of PAT, and PAT has no influence on whether or not an attacker has a route to you.
Re:The Ripe NCC Has Run Out of IPv4 Addresses
by icedchai on Thursday November 28, 2019 @03:28PM
(#21659983)
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.
Re:The Ripe NCC Has Run Out of IPv4 Addresses
by Dagger2 on Friday November 29, 2019 @05:29PM
(#21667196)
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.
Re:The Ripe NCC Has Run Out of IPv4 Addresses
by icedchai on Friday November 29, 2019 @08:54PM
(#21668010)
Security is not black or white, it is shades of gray. We'll just have to disagree.