• 35 Posts
  • 364 Comments
Joined 2 years ago
cake
Cake day: November 27th, 2023

help-circle


  • A fine start, but I think the plan could be made a bit more sustainable.

    1. Make a threat model. Hardware that is impenetrable today might not be as secure five years later as new security vulnerabilities are found. Who or what do you want to defend against?

    2. If you don’t use an OS that phones home, options without AI-enhanced wiretapping will still be around for years to come. There’s also several existing layers of hardware-related wiretapping to consider: the Intel ME, AMD PSP, BIOS, embedded controller firmware, SSD firmware, input peripherals, etc.

    3. I’d be happy to be proven wrong, but what you have sounds like specialty hardware, for which parts will become increasingly rare and expensive over 8 to 9 years. Ironically, common business-class laptops could be more future-proof by this metric, unless perhaps you plan on using one out in the field or in a metal foundry.

    4. Laptops are fundamentally like desktop computers, just in a portable form factor. Any security measure on a laptop can be more or less replicated on a desktop computer.






  • I daily drive Debian and have a few loose .deb packages and tarballs installed. Also enabled the Librewolf repo. It mostly comes down to an issue of manageability and possible conflicting dependencies. The ones I have installed don’t introduce any dependencies, so they’ve been trouble-free and have survived the Bookworm to Trixie upgrade. They are installed as a last resort option in the absence of a satisfactory equivalent via the official repo, Flatpak, or AppImage.

    Loose .deb packages can be installed and uninstalled like any other normal Debian package, but won’t be automatically updated and don’t have any compatibility guarantee. Tarballs are nothing more than a collection of files, which may need to be placed in system directories. You’re on your own for those since there’s no standard and automated way to manage them and it’s possible to overwrite important system files if unpacked and copied in blindly. It’s a good idea to keep a manual record of what was put where in case any issues with them pop up down the road.

    My personal ranking:

    Official Debian repo > Flatpak > AppImage > Docker/Podman > Snap >> Reputable and known compatible third-party repo > Loose Debian .deb > tarball > Loose Ubuntu .deb >> Unfamiliar third-party repos and PPAs

    There are certain occasions where a loose .deb or tarball won’t hurt, but sticking to options further up the list closes off the biggest routes of breaking Debian.







  • monovergent@lemmy.mltoLinux@lemmy.mlAntiviruses?
    link
    fedilink
    arrow-up
    2
    ·
    12 days ago

    I’m more concerned about rogue browser extensions that may be innocent when you install them, but then change owners, and after an update that you don’t even notice are going to do bad things.

    Exactly why the only extensions on my browser are uBlock Origin and LibRedirect. Was a victim of one user agent switcher extension that went rogue back in the day.





  • Using redlib to lurk on a handful of niche subs. Mostly as inspiration for my hobbies. Chief among them was r/thinkpad, but I’ve since weaned off them as they seem to be developing a phobia or even contempt for my favorite old ThinkPads. Yes, they’re over a decade old and not for everyone, but that doesn’t mean they belong in the e-waste pile. Or maybe they do so I can come pick them up.

    It’s also still home to many helpful support threads and tutorials, unfortunately.



  • Seems reasonable to me, although I might be lacking perspective since my latest hardware is already 6 years old.

    In previous years, my criteria was to upgrade once the hardware was holding back my workflow and productivity. But with Moore’s Law coming to a plateau, I’ve upgraded my RAM, GPU, and SSD not because I have to, but just because I got an very good deal on them.