this post was submitted on 27 Oct 2023
66 points (89.3% liked)

Apple

17339 readers
105 users here now

Welcome

to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!

Rules:
  1. No NSFW Content
  2. No Hate Speech or Personal Attacks
  3. No Ads / Spamming
    Self promotion is only allowed in the pinned monthly thread

Lemmy Code of Conduct

Communities of Interest:

Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple

Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode

Community banner courtesy of u/Antsomnia.

founded 1 year ago
MODERATORS
all 6 comments
sorted by: hot top controversial new old
[–] [email protected] 33 points 11 months ago* (last edited 11 months ago) (1 children)

In case anyone hasn’t read the article, the bug that exposed the real MAC address is fixed in 17.1, released today

[–] [email protected] 4 points 11 months ago (1 children)

I take it that it'll also come as a security update for older versions of iOS like 15?

[–] Nogami 1 points 11 months ago

If you say so.

[–] randomaccount43543 1 points 11 months ago* (last edited 11 months ago)

https://www.macworld.com/article/2118771/ios-17-1-private-address-security-hole-fix.html

iOS would respond to address requests with a private address as the source, which made it seem like the feature worked. However, the researchers found that the real, actual MAC address was provided in a different part of the request-response

That seems like a really sloppy implementation of the feature 😂 I’m glad they finally fixed it but how did it take three years to fix this!?