News for hackers. Stuff that matters.
Re:The Legacy of Peer-to-Peer Systems by dinosaurdynasty on Thursday December 01, 2022 @08:17PM (#33825519)
NAT punching definitely tells other peers your NAT's IP address (and often your local address too, but that's less important).

Unless you're behind CGNAT, your NAT IP can often be used to find your neighborhood with public information. With private information (a legal challenge for example) you can find the exact subscriber/house.

Re:The Legacy of Peer-to-Peer Systems by littlestymaar on Friday December 02, 2022 @05:01AM (#33828667)
> NAT punching definitely tells other peers your NAT's IP address

Yes, and that's all you share, so when the NAT is shared with other people (like other students on a campus for instance, or other customers of your phone mobile phone carrier) the amount of info that can be collected is much lower than if you have a public IP address for your computer.

> Unless you're behind CGNAT

Did you read what I wrote above, when I said: “at least when we're talking about a NAT you share with other people, not just your ISP box's NAT”.

> (and often your local address too, but that's less important).

Here you're mixing up the hole-punching part with the signaling protocol (ICE, which have had this issue in the past, before browsers switched to mDNS[1] instead of private IP addresses in ICE candidates).

[1]: https://groups.google.com/g/discuss-webrtc/c/6stQXi72BEU?pli...

Re:The Legacy of Peer-to-Peer Systems by dinosaurdynasty on Friday December 02, 2022 @11:01AM (#33832274)
You need a signaling protocol to do hole punching.
Re:The Legacy of Peer-to-Peer Systems by littlestymaar on Friday December 02, 2022 @03:51PM (#33836717)
The two are working together to establish a p2p connection behind a NAT but that doesn't make them equivalent. It's like saying “UDP sometimes leaks your local IP address”, that's factually inaccurate.