I’m the Never Ending Pie Throwing Robot, aka NEPTR.

Linux enthusiast, programmer, and privacy advocate. I’m nearly done with an IT Security degree.

TL;DR I am a nerd.

  • 1 Post
  • 271 Comments
Joined 1 year ago
cake
Cake day: November 20th, 2024

help-circle

  • I have been liking CachyOS as well. I reluctantly switched from Fedora after I kept getting weird problems (definitely a “my PC” thing, I wish I could upgrade).

    Features I like about Cachy:

    • Auto-setup of snapper btrfs snapshoting (my fav feature of openSUSE) on all bootloaders (I like the simplicity of limine)
    • Gaming ready fork of kernel-hardened, with some changes, including allowing use of unprivileged namespaces (needed by Bubblewrap/Flatpak/Firefox/Chromium to avoid the need of a SUID binary)
    • AUR (cus it is Arch)
    • Update service which updates from all installed sources (pacman, Flatpak, AUR)

    What I wish was different:

    • Inclusion of a full system Mandatory Access Control policy (SELinux preferably)
    • Compatibility with hardened_malloc (idk why but on Cachy, GTK apps crash because glycin bubblwrap commands fail)

  • The point of my comment wasn’t that OP was in “real danger” if they showed local IPs, just that it doesn’t hurt. Never give more information than necessary. I censor usernames and filepaths on any screenshots of the terminal, even though if an actor has the kind of access to utilize that information I am probably already fucked. I think it is good practice to always scrutinize the information you give out willingly.




  • N.E.P.T.R@lemmy.blahaj.zonetoPrivacy@lemmy.mlPrusa Printers Firewall Logs
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    12 hours ago

    I was taught in my IT Sec classes to avoid sharing any unnecessary information. Information on private IPs can be used to better understand your network, allowing a threat actor to better navigate your network without needing to do ip scans (which are very obvious and should trigger even basic detection). While it is most likely pointless (since OP probably isnt at risk of targeted attacks), it is still good opsec.


  • I much prefer the looks and feel of GTK4 libadwaita apps over Qt6. I switched to KDE Plasma after using GNOME for awhile because I wanted to see if I noticed any improvement in stability, I want to theme my apps, and I prefer to avoid extensions (it is a security risk). I still very much miss GNOME with the 3-4 extensions that I installed, it just felt so much more polished, consistent, and free of bugs and broken features (looking at you theme search and desktop animations installer).



  • My personal reasons for disliking systemd (note: I still use systemd):

    • The lead developer of systemd has said multiple times that we should be fine with break POSIX if it means developing faster.
    • systemd has massive attack surface, making it easier to exploit and result in privilege escalation. It is a highly complex and large codebase that really shouldnt be given the trust of PID 0
    • systemd is not portable or modular.
    • It only just barely got musl support. Hope to see it improve in the future.
    • systemd is much slower than other inits (eg. dinit, s6, openrc)
    • systemd being the go-to init encourages developers to more heavily depend on it, making it difficult for distros without systemd

    The biggest feature I like about systemd is run0, though I wish it was a drop in replacement for sudo. Secondly, I do like that services can be sandboxed.