Security

http://www.cso.com.au/article/547177/apple_randomises_mac_addresses_ios_8_killing_off_key_ad-tracking_tool/

Has anyone played w/ iOS 8 beta & have you ran into any issues w/ Airwave monitoring, or with any logging or tracking functionality?  

--Raf

Even so, will this not affect ClientMatch as it utilizes client probes?  I see this as potentially causing more issues, especially when troubleshooting a client association issue.  If you suspect a client probing issue, how are you going to identify the client probes with a packet capture?

Does anyone know if this will prevent MAC authentication from taking place?

If it probes the network with a random MAC but authenticates with its own correct MAC, i dont see that this should prevent MAC authentication from taking place.

On the other hand, if MAC authentication is in place as part of a layered security model, should the random MAC be in the list (is this going to be chosen from the Apple agreed list??) this could in effect authenticate a non authorised device, causing a security breach to the network

TIA

G

I think that's the burning question -- how will these devices play with virtual beacons/11k, and legacy-mode client-match?  Apples already are one of the rockier platforms for match/steering and this feature doesn't bode well.  Hopefully it completely turns off while enterprise authed.

Still remains to be seen what the effects will be, but once the device is actively associated to your wireless network it use it's own MAC-address. There is no ClientMatch etc before association right?

Tho - a system counting the number of MAC-addresses "probing the Air" will/might be worthless since all i-devices will probe with different MAC-address each time.