• 3 Posts
  • 39 Comments
Joined 2 years ago
cake
Cake day: August 21st, 2023

help-circle




  • You can start with dpigs. Then start marking packages automatically installed with apt-mark. aptitude may be a good frontend when removing a lot of packages, you can mark entire categories, like libraries, as automatically installed.

    Pay attention to the package headers when removing packages. You don’t want to remove essential packages.





  • As a finn, I understand that there are probably legal reasons for doing this.

    I just wish they would be transparent and share those reasons with us. The Linux kernel is certainly not the only free software project that is impacted, if this comes straight from EU/US sanctions. Maintainers of other projects have a lot of interest in what is happening.

    Transparency is also important because if EU/US policy/sanctions are causing issues for free software projects, then that discussion needs to be public, so that there is a chance to amend the policies if necessary.







  • Heh, Distrobox came to my mind when writing my comment. I haven’t used it enough to recommend it yet though.

    I recall there are some other development container projects, but can’t remember the names right now.

    Development containers are nice in theory. In practice, sometimes development environments are so complex that it might not be worth the trouble. But it’s good to have options.


  • Distro packages don’t really matter much in my experience. You either use project-specific package management or install stuff with Homebrew or Nix package manager. Sometimes maybe even containers.

    One problem with distro packages is that you can only install one version. And in practise a lot of software projects have outdated dependencies. Sometimes you have multiple projects with conflicting version dependencies.






  • ouch@lemmy.worldOPtoLinux@lemmy.mlVPS encryption
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Thanks for the comments. I agree on the general consensus, that once an encryption key enters the VPS, the encryption is compromised.

    However, I’m thinking more in practical terms, eg. the service provider doing just casual scanning across all disks of VPS instances. Some examples could be: cloud authentication keys, torrc files, specific installed software, SSH private keys, TLS certificates.