I am not satisfied with Linux’s security and have been researching alternative open source OS for privacy and security So far only thing that’s ready to use is GrapheneOS (Based on Android) but that’s not available on desktop (Though when Android release Desktop mode it may become viable)

Qubes OS is wrapper around underlying operating systems, so it doesn’t really fix for example Linux’s security holes it just kinda sandbox/virtualize them

OpenBSD is more secure than Linux on a base level but lack mitigations and patches that are added to linux overtime and it’s security practices while good for it’s time is outdated now

RedoxOS (Written in Rust) got some nice ideas but sticks to same outdated practices and doesn’t break the wheel too much, and security doesn’t seems to be main focus of OS

Haiku and Serenity are outright worse than Linux, especially Haiku as it’s single user only

Serenity adopted Pledge and Unveil from OpenBSD but otherwise lacks basic security features

All new security paradigms seems to be happening in microkernels and these are the ones that caught my eyes

None of these are ready to be used as daily driver OS but in future (hopefully) it may change

Genode seems to be far ahead of game than everything else

Ironclad Written in ADA

Atmosphere And Mesosphere Open Source Re-implementation of Nintendo Switch’s Horizon OS, I didn’t expected this to be security-oriented but seems like Nintendo has done a very solid job

Then there are Managarm, HelenOS, Theseus but I couldn’t figure out how secure they are

Finally there is Kicksecure from creators of Whonix, Kicksecure is a linux distro that plans to fix Linux’s security problems

if you know of any other OS please share it here

    • dsemy@lemm.ee
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      edit-2
      8 months ago

      If you are so qualified to talk about this, why don’t you provide any details at all, instead of repeating yourself?

      Edit: btw why would they even do “marketing”? It’s a non-profit free software project.

        • dsemy@lemm.ee
          link
          fedilink
          English
          arrow-up
          9
          arrow-down
          1
          ·
          edit-2
          8 months ago

          All I see is a bunch of drama. Daniel Micay is also no longer the head of GrapheneOS.

          IDK maybe beyond the wall of text there is some actual technical criticism, but I’m not going to sift through a bunch of unrelated pictures to find it.

          GrapheneOS very recently reported two CVEs affecting Android, with one not affecting GrapheneOS due to their mitigations.

          GrapheneOS has many features which are clearly visible to users and don’t really exist elsewhere - eSIM without Google Play, sandboxed Google Play, additional “Sensors” permission just to name a few.

          Edit: I watched the Louis Rossmann video, https://www.youtube.com/watch?v=4To-F6W1NT0, and he also only talks about drama related to Daniel Micay (while clearly not saying anything negative about the project on a technical level).

            • dsemy@lemm.ee
              link
              fedilink
              English
              arrow-up
              2
              ·
              8 months ago

              This argument is going nowhere.

              https://grapheneos.org/features lists features of GrapheneOS which differentiate it from AOSP. Are you claiming this is all fake?

              Most of the security measures are something you can take with lots of Android devices, and is nothing exclusive to Pixel/Graphene fairy tales.

              Is the Pixel 8 not the first device to support MTE? Is hardened_malloc pointless? And I literally listed 3 more features exclusive to GrapheneOS in my last comment.

                • dsemy@lemm.ee
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  8 months ago

                  hardened_malloc is a replacement for the libc function malloc. It is not part of Linux.

                  MTE is hardware-based, and is in fact restricted to Pixels currently (8+) AFAIK.

                  As I said in my first comment to you, do more research.