Add toggle to enable/disable insecure settings

[Martí Climent (marticliment)]

Certain features, such as custom command-line arguments, and future ones such as pre-install and post-install scripts, pose an important security risk. They should be disabled by default, and in a way that a remote, unauthorized agent cannot manually enable this features.

• Implement secure settings (can only be changed with administrator permissions, yet they should be user-based)
• Create a settings page to handle these secure settings. Create a UI warning to enable and disable them.

[mrixner]

Does this enable the implementation of #3038 as well? Or do you still have reservations about that?

[Martí Climent (marticliment)]

Yeah, it does. However, I want to do a generic pre and post install steps, to allow for more things aside from custom commands (kill an app before updating, cleanup after update, etc.)

[mrixner]

OK, I'll leave that one to you then, but I'm happy to help if you would like.

[Martí Climent (marticliment)]

Wait this is not supposed to be closed