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

help-circle

  • pacman is the best and I’ll stubbornly refuse to entertain any other opinion. It’s in my experience the least likely to just randomly rip the system to shreds. I don’t know if it has more through prechecks or what bit I’ve had debian and Fedora (apt and dnf) rip the system asunder trying to jump multiple major versions in an update of a system that hadn’t been online in a long time.

    I don’t care if jumping multiple releases at once “isn’t supported” it shouldn’t be that frail and arch will happily update something many years behind as long as you update the keyring.

    Even in the event your system somehow does get hosed you can fix almost everything by just chrooting in, grabbing the static pacman binary, and running “pacman -Qqn | pacman -S -” I’ve recovered systems that had the entire /bin wiped (lol oops moment with a script) and as far as i know apt and dnf have no equivalent easy redo all.









  • They are amazing but at the end of the day they are still humans and they can make mistakes. In the YouTube video referenced one of the C devs is heavily against rust.

    Decided to go look for CVEs from code the guy manages (Ted Ts’o) I found these

    CVE-2024-42304 — crash from undocumented function parameter invariants

    CVE-2024-40955 — out of bounds read

    CVE-2024-0775 — use-after-free

    CVE-2023-2513 — use-after-free

    CVE-2023-1252 — use-after-free

    CVE-2022-1184 — use-after-free

    CVE-2020-14314 — out of bounds read

    CVE-2019-19447 — use-after-free

    CVE-2018-10879 — use-after-free

    CVE-2018-10878 — out of bounds write

    CVE-2018-10881 — out of bounds read

    CVE-2015-8324 — null pointer dereference

    CVE-2014-8086 — race condition

    CVE-2011-2493 — call function pointer in uninitialized struct

    CVE-2009-0748 — null pointer dereference

    Do you see a pattern in the type of error here? It’s pretty much entirely memory related and right in the wheelhouse of something rust would just outright not allow short of just slapping everything into unsafe blocks.

    The Old Guard is not perfect, and they are acting as a barrier to new talent coming in. Sometimes change is good and I’m heavily in the camp that rust one of those times. Linus seems to agree as he allowed the code into the kernel which he would never do lightly or just because it’s fomo



  • LordKitsuna@lemmy.worldtoLinux@lemmy.mlProton Pass for Linux
    link
    fedilink
    arrow-up
    80
    arrow-down
    1
    ·
    11 months ago

    If we didn’t already have the perfect option that is bitwarden I would probably go for this. But there’s really no reason to switch away from bitwarden to this. It’s open source, gets regularly publicly audited, and nothing ever leaves your device unencrypted. So even if they had their data center broken into and all machines stolen physically I wouldn’t have to worry about my passwords



  • Yeah I don’t even understand the point. The vast majority of people don’t even need a client side firewall. The only time you need to worry about a client side of firewall is if you’re on a laptop that you actually take out of your house ever or on a university or otherwise shared network. At home it’s completely meaningless and a waste of CPU Cycles.

    There are significantly better ways to address security, like how to enable a sandbox like firejail or bubblewrap or enable things like apparmor, firewall is probably one of the most inconsequential parts of security these days because it’s all handled by the local router