4 ms·
I wouldn't like to perform update && upgrade (and also reboot!) automatically every day or so. Why? Because updates/upgrades are always something that should be
by Morgawr 12y ago
I wouldn't like to perform update && upgrade (and also reboot!) automatically every day or so. Why? Because updates/upgrades are always something that should be overseen by a capable administrator. Sometimes updates break, sometimes they override your personal config files with less secure default files, sometimes the system crashes and you're left in an inconsistent and dangerous state, etc etc.
I definitely don't want to automate my server's updates in such a way.
- azernik 12y agoI haven't looked too closely at this particular project, but if I were writing something similar, I'd explicitly make it hard to access any of the security-related settings, and make the defaults (for which upgrades are tested) secure by default. In this case, changes to security settings to deal with new threats would be distributed through the package update mechanism, not overridden by it. That is, the really interesting target user here is not the one who will drop into the command line to tweak /etc/ssh/sshd_config and then get annoyed when their changes are overwritten on the next update.
- blablabla123 12y agoIf you allow little configuration options, you could as well allow to easily reset the server to default. I mean a zero configuration server cannot be compared to a server that has > 100 users. The latter usually has a lot of custom settings which would a) easily get damaged during updated b) be lost when resetting the whole thing There is definitely a need for easily manageable servers that should be low on customization and maintenance.