• 2 Posts
  • 220 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle






  • The problem is always having the bad option being enabled by default. Not even the ads are the biggest problem. I didn’t even mention their current ads in the terminal. The problem is the same Microsoft is having now, that your keyboard input gets sent to an untrustworthy third party.

    Your comment got cut off. If you wanted to dispute the paid paid claim. It is about Ubuntu Pro, that’s literally all what the basic tier is. We recently even had the case where a patch with a highish CVE rating was only available to subscribers of the service. We also verified that the same patch was already available on Debian. Even without my anecdote it should be obvious why it is bad.






  • Not the person above, but if it is an issue you ever run into you are doing it “wrong”. Not really, but let me explain.

    Having it on a separate partition has a few advantages like different mount flags (e.g. noexec), easier backup management (especially snapshots) and some other benefits like using your home for a new installation (like OP wants to) or it prevents some critical failures in case you accidentally fill it up (e.g. partial writes or services cannot start).

    I often cannot decide on specific mount sizes either, because requirements may change depending on what you do. Hence I would just stick with some reasonable defaults for the installation and use some form of volume manager instead. If you want to use ext4, xfs etc I would recommend using LVM as it gives you a lot of freedom (resizing of volumes, snapshots and adding additional drives, mixed RAID modes etc) or there are btrfs, zfs or bcachefs to name the most common file systems which implement their own idea of storage pools and volumes.

    Never should you need to resize a partition, there are more modern approaches. Create a single partition (+ a small EFI partition somewhere) and never bother with partitions ever again. The (performance) overhead is negligible and it gives so many additional benefits I didn’t even mention. Your complaint is a solved problem.





  • sudo is not simply a tool to give admin privileges, but a tool to manage elevated permissions or run commands in a different users context.

    These things become a lot more relevant once you use the tools professionally. In a well configured system you are only allowed to run the things you are explicitly allowed.

    To be completely honest sudo is basically pointless in a single user context. There is almost no reason to even have it installed. It makes dealing with different environments easier though.

    Anyway as I said it does not matter in many cases if you are the systems administrator. On the other hand there is also no benefit in getting used to bad practices in case you have to unlearn them later.

    One more thing: what you suggest with chroot is one of the very reasons why you should not do that. You might have handed over the keys to break out of chroot. It is a well known vector which boils down to never run anything as root in a chroot environment.


  • sudoedit opens the editor as your user and just writes the file as root. For a single user who is also admin on the system this does not matter in many cases.

    In a multi user context you can easily escape your editor and run a shell which allows a non admin user to escalate their privileges. So from a security implementation standpoint this must exist and it does for this reason.

    Of course this also prevents some mistakes from happening and a bad plugin cannot destroy your whole system easily and so on. It boils down to good practice.