Hacker News new | past | comments | ask | show | jobs | submit login

Two more useful and related Apple KB articles:

macOS wireless roaming for enterprise customers https://support.apple.com/en-us/HT206207

About wireless roaming for enterprise https://support.apple.com/en-us/HT203068




This is an offtopic side-track/distraction, but I've been completely thrown by the masking in the screenshots and example CSV dump.

The first thing I'm distracted by in the expanded Wi-Fi menu in the first link is "Address: xx:x0:00:00:x0:00:00". wHaT wErE tHe 'x's bEfOrE?? Why mask out the first 1½ octets of the MAC when the first 3 octets are manufacturer-specific and (IIUC) would have been one of Apple's prefixes, and given that the assignment is apparently random¹ this would practically have leaked absolutely nothing. Next, the first half of the 5th octet is an 'x'. wHy??//? 𝖜𝖍𝖆𝖙 𝖉𝖔𝖊𝖘 𝖎𝖙 𝖒𝖊𝖆𝖓

Further down in the menu we have... OwO what's this™, 𝕒 🄷🄾🄻🄻🅈🅆🄾🄾🄳 𝕀ℙ 𝕒𝕕𝕕𝕣𝕖𝕤𝕤? "010.101.0.10"? Do I briefly switch to octal to parse that first octet? Pretty impressed the Mac in question is the network's router though - especially given it's a Wi-Fi network. Oh - sorry, you got a bit of sarcasm on you there, let me get it off :P

Then we have the scan window further down in the same article. OK, so the distribution of noughts and crosses :) is apparently correlated with the security setting (the protocols are all over the place and seem to represent different routers). I honestly don't get it.

Moving onto the next article, ...oh no the 'X's have gotten angry and are now in UPPERCASE! I wonder where "01:01:00:01:XX:01" is??? "10:01:10:01:X0:10" looks positively scary.

A small tangent is required to remark about how everything that has ever happens on an iPhone happens at 09:41 really has gone so far as to be unrealistic. The original idea was just to have the marketing materials acknowledge when iPhone went live at WWDC. These screenshots with the "scan result: 09:41:45 AM" are absurd, both because iOS 11 did not exist back then, and because it would not be possible to practically do a network scan and deployment at the exact same nanosecond the OS you're supposedly supposed to be using is being debuted. The one event categorically predates the other. Hmph.

OK, moving to the bottom of this article we get the... notascreenshotsoapparentlytheartdepartmentcantseeit™ CSV data. With 𝘤𝘰𝘯𝘧𝘶𝘴𝘪𝘰𝘯 inside©! Firstly, unfortunately I don't know how to do a "this SSID and this SSID within 10km of each other" search, so I don't know if ACES and Cuba are actually real, but what I can say is that while the first listed MAC address turns out to be invalid (makes sense), the second and third entries are Apple-prefixed - which doesn't make any sense since this is supposed to be a list of access points, not client devices - but in any case, both MACs are valid and resolve to a street address - 𝔀𝓪𝓽, 𝓪𝓹𝓹𝓵𝓮? 𝓾 𝓸𝓴? - and while the second MAC only has one entry, the third has a location history that includes an address <10 meters away from the second one. Hi developer who gets around!

¹ https://apple.stackexchange.com/questions/49948/differentiat..., http://www.coffer.com/mac_find/?string=apple




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: