News for hackers. Stuff that matters.
Re:IPv6 Address Unmasking via UPnP by aboutruby on Monday March 18, 2019 @08:21PM (#19426774)
I never realized an IPv6 likely contains the MAC address of the host, how did people not realized how terrible this design is.
Re:IPv6 Address Unmasking via UPnP by zamadatix on Monday March 18, 2019 @09:02PM (#19427090)
> When IPv6 was developed in the mid-90s, the Internet was not accessed by a large number of mobile devices and privacy was not the priority it has become today. To address these privacy concerns, the SLAAC protocol was updated with mechanisms that were termed “Privacy Extensions for Stateless Address Autoconfiguration in IPv6”, codified in RFC 4941. This allows for the IPv6 address interface identifier to be generated randomly. If the same interface identifier is generated for two devices in the same local area network, the Duplicate Address Detection (DAD) function of the IPv6 Neighbor Discovery Protocol (NDP) will resolve the situation.

Prior to those times tracking protection wasn't critical in protocol design (or most people's minds in general) and so using the MAC was a great way to self select an address without extra steps.

Re:IPv6 Address Unmasking via UPnP by sliken on Tuesday March 19, 2019 @01:18AM (#19428268)
IPv6 Privacy Extension as defined in RFC 4941 is commonly implemented and prevents this from being an issue.
Re:IPv6 Address Unmasking via UPnP by JohnFen on Wednesday March 20, 2019 @01:01PM (#19444187)
"Prevents" is overstating this a bit. The IPv6 Privacy Extension is a hack that doesn't completely mitigate this sort of problem. It's just better than nothing, and is all we have.
Re:IPv6 Address Unmasking via UPnP by sliken on Wednesday March 20, 2019 @01:37PM (#19444632)
How so?

With IPv4 you reveal the IP of your IP Masq/Nat router, which is often inside your home/business. It can be dynamic or static, but generally changes pretty slowly. There might be a single person behind that IP, or 100s.

With IPv6 your /64 is often inside your home/business. It can be dynamics or static, but generally changes pretty slowly. There might be a single person behind that /64, or 100s. Different outgoing connections see different IPv6 addresses, and they change over time (slowly).

Most importantly just like a mac address, the outgoing connections never use the IPv6 address based on mac address.

So how does the privacy extension not protect the privacy of users by hiding the mac address?

Re:IPv6 Address Unmasking via UPnP by JohnFen on Wednesday March 20, 2019 @06:11PM (#19447522)
> So how does the privacy extension not protect the privacy of users by hiding the mac address?

I never said it didn't. I stated that people overstate the protection the facility provides, not that it didn't provide protection.

The deficiencies of the privacy extensions have been discussed widely for years. A quick internet search will show the various criticisms and responses better than any reply I can make here will.

I should, however, clarify what I was trying to say -- I was not trying to say the privacy extensions aren't worthwhile. They're great, and people should use them!

What I was trying to say is that people often think of them as a panacea or a 100% solution. They aren't exactly that (what is?), and the nature of the design of the privacy extensions are such that they make other important network management activities more difficult.

My main criticism of PE (and it's not a showstopper sort of criticism) is that the extensions are hacky and it shows. They were thought up after-the-fact to try to mitigate a security mistake made in the original IPv6 protocol.

Re:IPv6 Address Unmasking via UPnP by sliken on Thursday March 21, 2019 @01:20AM (#19449435)
Sure, but the original parent was complaining about the mac address (not any larger privacy issues) and the PE does a good job of hiding the mac address and is enable by default in many common operating systems (Mac, Windows, Ubuntu, etc.)
Re:IPv6 Address Unmasking via UPnP by cesarb on Wednesday March 20, 2019 @10:46AM (#19442740)
IPv6 is old. Back then, not only servers but also desktops were commonly on a fixed public IP address, accessible from anywhere on the Internet. Hiding the MAC address would gain very little, since the IP address was enough to uniquely identify a host.
Re:IPv6 Address Unmasking via UPnP by icedchai on Wednesday March 20, 2019 @11:15AM (#19442998)
Back in the mid 90's, before NAT was common, we had public IP's everywhere, even with IPv4! Even my home network was on a /24 class C.
Re:IPv6 Address Unmasking via UPnP by subway on Wednesday March 20, 2019 @11:47AM (#19443352)
Even now, some large traditional sites put static public IPs on workstations. When I was a lbl.gov, you got a (minimally firewalled) public ip via dhcp, and the hostname sent by your workstation was used to create a dns record of foo.dhcp.lbl.gov. You could request a static address for your host, and you'd be assigned an even less firewalled ip along with a foo.lbl.gov record.

A decade later this still seems to be at least partly in place, as I'm able to browse the webserver running on an old colleague's desktop.

Re:IPv6 Address Unmasking via UPnP by 0xffff2 on Wednesday March 20, 2019 @01:22PM (#19444431)
Wow. I work for another US government agency down the road from LBNL, and here I can't even see many internal servers from my laptop because there is a firewall between the (wired!) laptop-accessible network and the inner ring that the servers are on.

I think my sysadmin group would have a collective heart attack if they saw that setup! It's quite incredible to me how independent various parts (and pseudo parts like the national labs) are from each other.

Re:IPv6 Address Unmasking via UPnP by subway on Wednesday March 20, 2019 @02:28PM (#19445255)
LBNL is an incredibly open, yet monitored network (in the spirit of the collaborative research that goes on there.)

You can be certain that most every packet in, out, or through the place gets captured and inspected by Bro (errr, I guess Zeek now. https://www.zeek.org/ )

I should also mention that not every host had a public IP. I worked with the group that managed midrange compute clusters, which were always behind NAT, with bastion login nodes.

Re:IPv6 Address Unmasking via UPnP by api on Wednesday March 20, 2019 @12:50PM (#19444045)
IPv6 was designed long before surveillance capitalism was a concern and before security in general was as much of a concern as it is today.

Addresses don't have to be assigned that way. There are other ways of assigning addresses including privacy addresses and DHCPv6. The address space is so big that just generating a random address, while not RFC, is "okay" on all but huge networks if you're working in a /64.

Re:IPv6 Address Unmasking via UPnP by throwaway2048 on Monday March 18, 2019 @10:37PM (#19427605)
Most OSes use opaque identifiers that are per prefix these days thankfully, that can not be tracked across networks or tied to mac addresses.
Re:IPv6 Address Unmasking via UPnP by cm2187 on Wednesday March 20, 2019 @10:46AM (#19442746)
Only if the network admin configures the DHCP to do so. I believe the default on most OS is a random suffix.
Re:IPv6 Address Unmasking via UPnP by oasisbob on Wednesday March 20, 2019 @11:56AM (#19443458)
Many IPv6 networks aren't even using DHCP, SLAAC (RFC 4862) is used instead.
Re:IPv6 Address Unmasking via UPnP by cm2187 on Wednesday March 20, 2019 @12:09PM (#19443598)
Yes, sorry, bad v4 habits. MAC or random addressing aren't even using DHCP, they are using stateless addressing.