- Status changed to Active
over 1 year ago 2:20pm 9 May 2023 - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Is this still relevant?
Clarifying current status after ~5 months of silence.
Allowing updating your codebase in production could be open some potential attack vectors.
Currently the update module in core also has this problem. To mitigate this the Update module allows you to set allow_authorize_operations = FALSE in settings.php which turns off this functionality.
Once Automatic Updates is in core there won't easy way to prevent a user with the correct permissions from turning on the Automatic Updates module and being able to update core, and other projects once we support updating them.
Consider adding a global "kill switch" mechanism in Package Manager, a boolean in settings.php like package_manager_disable = FALSE, which if set to TRUE would make all Package Manager operations throw an exception. That's one option;
Or we could just add global kill switch for Automatic Updates and other modules could follow the same pattern if they want to.
Decide if we should do this, and how. Then do it. Or don't. :)
TBD
TBD
TBD, but probably none.
Active
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Is this still relevant?
Clarifying current status after ~5 months of silence.