• 1 Post
  • 157 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle



  • Compared to Arch(-based): Accesing the latest packages. It’s not impossible, especially if you go for Debian testing repos, but it’s definitely extra work.

    Compared to special-purpose distros (i.e. gaming, portable, high security/privacy, pen-testing): Whatever their special purpose is will usually be harder to achieve.

    Compared to huge corpo distros (SUSE/Fedora and derivatives): Ease of more intricate setups and maybe some security testing.

    Compared to Ubuntu: Paying a corporation to not withhold security patches from you.





  • In short: No. It’s getting better, but Flatpak is by no means secure. Think of it as a Windows .exe or .msi with some (not that hardened) rights management.

    In addition, Flatpaks afe often community made and not even “signed” (which is not really a thing in Flatpak to begin with (yet) ((afaik))).

    Something really secure would be a container, something really, really secure would be a VM, something really, really, really secure would be a separate machine. Flatpak is less secure than the least secure thing in this enumeration.












  • You can reinstall stuff without uninstalling it first (yay -S <package>). To add to the other comment suggesting a driver reinstall, you can use downgrade to revert back to old versions (and also to keep it fixed till you wanna give it another go, don’t forget if you do so tho!).

    Moreover, set up snapshots! They provide a very straightforward way to recover from failed updates.

    If you are on btrfs, you need: snapper, snap-pac, btrfs-assistant (optional, but provides a GUI and more automation…)

    If you are on ext4: timeshift, timeshift-autosnap

    Im both cases you need to create a profile for root (/), although when it comes to Timeshift I think you need (/ want to) exclude /home. (On the default btrfs setup, you don’t need to do this, because /home is it’s own subvolume).