I wholeheartedly agree; locking down systems is a feature, not a bug.
I would go even further and say it's not just so in the users minds, it is also so in the admins mind, whether that's a business setting where we have to make sure thousands of workers don't accidentially brick their PC (or worse: cause an infosec issue), or a family setting.
Though I have to say, that lockdown-feature comes with a rather heavy price tag attached, because, well, the systems in question do a whole lot more than just make the locking down easy, do they?
It would be great if commonly used Linux Desktop Environments allowed for a switchable (with root-privileges) "Lockdown". I'm aware that this is possible already, but requires too many steps and is too error-prone. What I want is a simple on/off-cmd offered directly by the Desktop-Suite for me to issue as root.
That would allow people like you and me to setup computers for non technical people to use easily, whith the benefits of both an open system, and the stability a locked down system provides.
I would go even further and say it's not just so in the users minds, it is also so in the admins mind, whether that's a business setting where we have to make sure thousands of workers don't accidentially brick their PC (or worse: cause an infosec issue), or a family setting.
Though I have to say, that lockdown-feature comes with a rather heavy price tag attached, because, well, the systems in question do a whole lot more than just make the locking down easy, do they?
It would be great if commonly used Linux Desktop Environments allowed for a switchable (with root-privileges) "Lockdown". I'm aware that this is possible already, but requires too many steps and is too error-prone. What I want is a simple on/off-cmd offered directly by the Desktop-Suite for me to issue as root.
That would allow people like you and me to setup computers for non technical people to use easily, whith the benefits of both an open system, and the stability a locked down system provides.