OTOH, 802.1x is not very frequent in networks outside enterprise environments, where you should know about the fact that the connection is secured with 802.1x anyway; or get a preseeded / provisioned system which already takes this into account.
Purely technically, seems to me like going out of our way to listen for 802.1x packets (when we currently don't do so for anything, except the fact that there is a carrier, or maybe dhcp through our dhcp client...) would mean having way more logic than entirely necessary in NM. On the other hand, 802.1x is handled by wpa-supplicant on wired interfaces, not directly NM, so we *could* just run in regardless and maybe ask to be notified if there is a change in security. Regardless of the concerns expressed above, this is really an upstream issue and should be dealt there. Could you please open a bug report at GNOME (you can follow the instructions here: https://wiki.ubuntu.com/Bugs/Upstream/GNOME), explaining the request so that it could be tackled by the upstream developers? Thanks in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783560 Title: Automatically detect 802.1x on wired network and ask for details -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
