I understand that this can be disabled. Do you think a *default setting* that allows this is sensible?
If this was applied to other functions ( cups is the example I gave), it would be equally easy for the admin to disable the default if desired and allow more users to access that configuration - but Ubuntu doesn't do that for cups, yet it takes the opposite view for nm-applet /network- manager? Why is this not restricted by default, and set to allow the admin to loosen the permissions as appropriate? Simple example: home user with kids sets up xdmcp on local network because it's an obvious and easy way to save money on hardware and take advantage of the network transparency of X. Kids discover that they can disconnect parents by clicking on the applet. Parents have no unix training and are apoplectic that this is possible... Think outside the sysadmin mindset for a moment and you will see my point. Most people will run screaming from commands like chmod , and I stick to my view that the groups and permissions for this should be restricted by default. There could be a popup dialogue that informed users that their admin needs to loosen the restrictions as required. -- network-manager allows an unprivileged user to disconnect the network from xdmcp login https://bugs.launchpad.net/bugs/104173 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
