Nice. Software developer, gamer, occasionally 3d printing, coffee lover.

  • 0 Posts
  • 62 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle





  • I’ve had bad tinkering break my system before, but never had an update break it irreversibly. The closest would actually be on Silverblue itself, when an update to the kernel was using different signing keys that cause the system not to boot. Fortunately it was simple, I selected the previous deployment and I was in (on a non versioned OS I would have selected the previous kernel which most are configured to retain the last few). A quick Google revealed Ublue had a whole kerfuffle and after verifying it was legit, I enrolled the new certs into my MOK.

    Although one time on Arch I had installed an experimental version of Gnome from one of their repos, and was pleasantly surprised when that version finally released and I removed the experiment repo and did an update absolutely nothing at all broke. Nothing.


  • Zikeji@programming.devtoLinux@lemmy.mlVPS encryption
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 months ago

    LUKS, or anything that relies on the server encrypting, is highly vulnerable (see schizo@forum.uncomfortable.business’s response).

    Your best bet would be encrypting client side before it arrives on the server using a solution like rclone, restic, borg, etc.







  • The article that user links is referring to GrapheneOS (and other OSS software) as not being “free software” - and they (GNU) delves into it more here.

    Basically, GNU is saying software shouldn’t claim to be free and open source if they contain non free binaries / other non-free blobs.

    The nuances between FOSS and OSS can be confusing. GrapheneOS is not claiming to be FOSS.