Our News Team @ 11 with host Snot Flickerman

  • 1 Post
  • 331 Comments
Joined 10 months ago
cake
Cake day: October 24th, 2023

help-circle



  • Crypto is never going to solve the issue of data-in-transit will always have a chance to be intercepted, even if it’s encrypted.

    Crypto doesn’t magically make all the internet infrastructure your property. It’s still bits passing through routers and switches that none of us actually have control over.

    I think crypto is held back by it’s insistence that it traverses other people’s property and relies on other people’s computations/CPU cycles to exist as a good thing, and not a bad thing. Just personal opinion, anyway.

    There was never anything crypto couldn’t do that a database couldn’t reasonably do as well, with the right configs.












  • You could set your staging environment PCs to be checking for updates hourly and installing them daily.

    You could set your other PCs to just be downloading the updates daily but only install them on certain days of the week.

    That means your staging servers could be constantly updated, but your other servers only download the updates, but wait until a certain day to install them.

    I’m not sure you can set the timer based on a specific package being updated without some bash scripting alongside checking for which things are getting updated in your staging servers, and then using that script to update the unattendedupgrades control files on your second and third tier PCs in the fleet to adjust when they’re supposed to install those updates.

    I can’t currently find anything on prohibiting specific packages or only installing selected updates from the downloaded updates. Perhaps you could use a mix of systemd downloading the updates and a cronjob for installing them?


    Further, Ubuntu/Debian is technically already doing this as well. They already have staggered rollouts in APT.

    If you’ve ever updated via command line and seen the phrase “These packages have been kept back” or “these following upgrades have been deferred due to phasing” it’s because they’re purposefully withholding those updates from you, to make sure they roll out safely to everyone. That way, if a handful of users who get a phased rollout have issues, the rollout can be undone before it goes out to everyone.