3 ms·
some functionality might only be possible by being insecure, thus a security update may have to remove functionality.
by bryanrasmussen 5y ago
some functionality might only be possible by being insecure, thus a security update may have to remove functionality.
- KronisLV 5y agoIn that case, we're probably (hopefully) talking about air gapped environments, like medical devices that aren't networked or internal corporate networks with very particular host access rules. In those cases, you might truly want no updates of any kind, with which i agree - updates should always be compatible with the "opt out" approach, or even do "opt in" (like Debian has an unattended upgrades package, for example: https://wiki.debian.org/UnattendedUpgrades https://wiki.debian.org/UnattendedUpgrades). That said, due to the world that we live in, it's risky to forgo any sorts of security updates, especially in the context of networked devices and systems!
- bryanrasmussen 5y agoI mean I was thinking more about the thing were WMF files used to allow you to run scripts inside the files which created security issues https://www.computerworld.com/article/2826084/what-you-need-to-know-about-the-wmf-vulnerability.html https://www.computerworld.com/article/2826084/what-you-need-... - lots of functionality that is enabled to make things easier for applications to do stuff is fundamentally insecure, so pushing a solution to fix the security issue will sometimes lead to remove functionality from the application that the user has to accept. So the premise that we could remove security issues but not touch functionality seems utopian.
- selfhoster11 5y agoNope. A security update that removes a feature should add a checkbox to a control panel that's pre-checked to disable functionality. The system administrator is prominently notified that they must take a look at whether this breaks their use case, and make the right call following risk assessment.