> * New unknown network devices should require confirmation
These two are the most confusing behavior from current OSes for me - I understand why there is network activity happening while machines are locked for some processes, but I am not entirely sure I understand loading new hardware devices when in a locked state and/or without user interaction of some sort. This suggests an oversight in my mind, and my feeble mind can't think of good reasons why it is this way.
The same issue with new network interfaces - it seems like it's a very intentional action that should be done by the user and not something that should happen automatically, and especially not in a locked state.
Would the same behavior happen on a least privilege account or even a restricted privilege account like something with parental controls enabled? I know that software changes are controlled via this, but hardware changes being allowed seems unusual.
I think udev is a bit to low level for this. NetworkManager & co. would be the right place IMO. Maybe this could even be considered a security bug with them.
Some suggestions:
* When the GUI is locked, activating new USB devices or even activating a connection via a cable to the ethernet port should be delayed until it is unlocked and (optionally) the user confirms that it's ok.
* New unknown network devices should require confirmation
* A network interface that announces a subnet larger than /24 or /16 (for IPv4) should require a confirmation by the user.
What scripts and hooks are being called whenever there is a change to USB and networking? That would be the place to start. Can there be a /etc/udev/rules.d/ rule that matches all devices?