The behavior may or may not be intented; regardless, I assert that it is incorrect.
It is not for Network Manager to dictate security policy for files that I have created. The file exists on the system already, so any information leak to other users *has already happened*. If Network Manager wants to enforce permissions on system configs when it /writes/ them, then that's ok with me, but it should not attempt to enforce security *on behalf of the wireless network*, which is not its role and not my concern as a user who created this file.
This is a usability problem introduced by inappropriate pseudo-security measures in Network Manager.
The behavior may or may not be intented; regardless, I assert that it is incorrect.
It is not for Network Manager to dictate security policy for files that I have created. The file exists on the system already, so any information leak to other users *has already happened*. If Network Manager wants to enforce permissions on system configs when it /writes/ them, then that's ok with me, but it should not attempt to enforce security *on behalf of the wireless network*, which is not its role and not my concern as a user who created this file.
This is a usability problem introduced by inappropriate pseudo-security measures in Network Manager.