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.

  • 0 Posts
  • 92 Comments
Joined 3 months ago
cake
Cake day: November 20th, 2024

help-circle






  • N.E.P.T.R@lemmy.blahaj.zonetoLinux@lemmy.mlHardening Mint
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 days ago

    I watched the video. Yes, if your sandbox config is weak then it will allow sandbox escapes. I agree the should default should be a secure sandbox. Bubblewrap offers the opportunity to shoot yourself in the foot. Look into the others tools I mentioned if you want to see different implementations. Sydbox is the one I think is the most interesting.



  • N.E.P.T.R@lemmy.blahaj.zonetoLinux@lemmy.mlHardening Mint
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 days ago

    Hardening is not useless, but it doesnt fix the architectural issues with Linux and its outdated threat model. That article says the same thing. It isnt an all-or-nothing situation, hardening still improves Linux security. Projects exist like SELinux, Bubblewrap, Crablock, Sydbox, and Landlock. Efforts to harden GNU/Linux have been made, like Kicksecure (Debian) and Secureblue (Fedora Silverblue), which protect against many threat vectors, but not perfect obviously.











  • Even if documentation can be time-consuming, it is such a lifesaver and makes the whole process of coding much smoother. It means not as much time wasted backtracking. If you think there is any part of your code you won’t understand when you coming back to it, document, document, document.

    Sometimes I write some multiline psuedocode comments or/and an explaination of specific choices, especially those invisible choices you make while debugging that aren’t apparent when your just reading through your code.

    Good thing to do is make code that is generally readable too lol.