Skip to content
This repository has been archived by the owner on Sep 9, 2024. It is now read-only.

Disable MAC-address randomization #35

Open
jornane opened this issue Aug 26, 2020 · 2 comments
Open

Disable MAC-address randomization #35

jornane opened this issue Aug 26, 2020 · 2 comments
Labels
android Android related apple iOS/MacOS related documentation Improvements or additions to documentation enhancement New feature or request

Comments

@jornane
Copy link
Member

jornane commented Aug 26, 2020

A new security feature for iOS, and possibly also Android, is MAC address randomization.

Currently, eap-config has no way to indicate that this should be turned off, and I don't know if we can disable this through a profile, but I made this ticket so we can discuss this.

@jornane jornane added documentation Improvements or additions to documentation enhancement New feature or request apple iOS/MacOS related android Android related labels Aug 26, 2020
@spaetow
Copy link
Contributor

spaetow commented Dec 8, 2020

Apple allows this to be switched off through a .mobileconfig file.

@pauldekkers
Copy link
Member

I understand platforms will warn about randomization being turned off in the future; so it may indicate a label that the connection is insecure (just like it labels networks that use WPA1 today).

Maybe good idea to have a broader discussion about the feature in eduroam. We don't need the MAC-address to be persistent in eduroam. Randomization is fine. If this causes issues with DHCP exhaustion at organizations or identifying users, that's a problem anyway with guests and users that enable MAC randomisation outside of the profile configuration.

Anyway, biggest issue I guess before implementing is that it's not possible to flag in .eap-config.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
android Android related apple iOS/MacOS related documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants