DigitalDilemma

  • 0 Posts
  • 35 Comments
Joined 2 years ago
cake
Cake day: July 22nd, 2023

help-circle




  • Others have answered why this isn’t a memory leak as such and is not as big a deal as you may think.

    But if you are still concerned, you can reduce it, even if doing so is a bad idea.

    1. You’re running it natively which means you’re probably using a systemd .service file to manage jackett. Research the .system setting “RuntimeMaxSec” - that will force a restart of the service every N seconds and prevent it growing. (This is a bad idea, but if you want to boss it around, you can)

    2. Run it in docker and force a max memory setting. Docker will prevent it using more than you set. You can also restrict cpu usage this way too. docker-compose example goes something like:

    deploy: resources: limits: cpus: 0.5 memory: 100m








  • Canonical is UK based, so scrub that.

    But Redhat, Rocky, Alma are all owned by US legal entities and can absolutely be legally forced to do as you describe.

    Technically blocked is something else, mind. We’re clever, resourceful and motivated people and US laws wouldn’t directly affect us.

    However - you’re thinking small. US influence of IT is massive. Routers, servers, hardware of all levels. The most enterprise level software is US led. All of these things can be restricted, or tarriffed heavily, or sanctioned entirely. If the US wants to hurt the rest of the world, it just has to tell Broadcom to turn off vmware outside of America. Ditto Cisco, Ditto Dell, Ditto… etc etc. Sure, it would be illegal, but does the American government care about that?

    Anyone telling you that “Y won’t happen because it’s unthinkable” clearly hasn’t been paying attention this year.







  • Debian stable is as hassle-free as you’ll get.

    It sounds like your issue is more with having to migrate to a new laptop. Firstly - buy laptops that are more linux compatible and you’ll have fewer niggles like with sound, suspend and drivers.

    Secondly - use “dpkg --get-selections” and “–set-selections” to transfer your list of installed software across to your new laptop. Combined with transferring your /home directory, user migration can be speeded up.


  • I think you make a good point, but it’s one that affects any anti-malicious protection. How do you know that the anti-virus warning you get on Windows is legitimate and not a false alert? Or that the Apparmor block wasn’t a misfire? Selinux is no better nor worse in principle than those.

    In all cases, you need to stop and figure out what’s actually going on. That’s one benefit of all these things - they make you pause and, hopefully, think, when something is outside the norm.

    And yep, they can be bypassed and they need to be able to be bypassed. If someone is lazy or not knowledgeable enough to make the right decision, or even just in a hurry, then they are at risk. No automated system can protect entirely against that.


  • Permissive mode, and yes, you absolutely can. That shows warnings but doesn’t actively block. But you still benefit from running setroubleshoot to actually figure out what and why it’s blocked something, and how to mitigate that.

    Permissive is also good in that you can get a bunch of blocks reported at once, instead of having to step through one at a time, which can be useful.