337
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Oct 2023
337 points (100.0% liked)
Technology
59334 readers
4252 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
this is whitewashing Apple. It was introduced in iOS 14. A trillion dollar company like apple should have had this fixed long before.
Lol, and Apple didn't even "discover" it themselves. It was 2 unaffiliated security researchers who did. Who knows if they even implemented any logic besides the UI.
If you had read the article, you would have known that the bug relates to a very specific field inside a multicast payload and a network-specific unique MAC address is generated and retained as advertised. I'm not defending Apple; just reiterating the facts.
The way multicast works is that the destination mac address starts with 01 00 5e and then next 3 octets (mac addresses are 6 octets long) are copied from the IP address lower octets. The mac address is always this when building the L2 headers for the packet.
It's not specified what precisely is provided in the payload of the multicast body. I suspect that the original MAC address is included in something like a Bonjour broadcast, but I wasn't able to find any documentation that confirms that.
not if it was intentional. I mean apple bends over for authoritarian governments around the world. This could easily be used as a state surveillance apparatus and casually "fixed" when discovered down the road as a "bug".
yeah I agree that it was intentional. I can't believe Apple didn't properly test this feature. But I didn't want to speculate without actual proof