Hello, making this post to get some honest, and technical opinions about GrapheneOS. Please do not be bother by this question. No drama here pls 🙏. I’ve heard that there is some of the google code into the “sandbox” feature. Say your opinion below! 👇👇

    • 乇ㄥ乇¢ㄒ尺ㄖ@infosec.pub
      31·
      8 months ago

      That’s also not accurate, GOS comes fully degoogled, and doesn’t include any GAPPS or Google Play services, you have to install them yourself if you want compatibility with Google Apps or some banking apps

      even though they are sandboxed. There is no way it can be more degoogled than LOS

      That’s just false, even LOS isn’t fully degoogled and it still connects to Google in the background for necessary connectivity checks ( e.g. DNS ) and Esim activation for example

        • 乇ㄥ乇¢ㄒ尺ㄖ@infosec.pub
          2·
          8 months ago

          it couldn’t be as degoogled as LOS because LOS is vanilla

          This is about to change since LOS are about to include MicroG by default in future releases… Or so I heard from some Mastodon users who shared screenshots about an LOS update that installed MicroG

          GOS is private and secure more than any other ROM, but once you install the Unprivileged play store you lose some of that privacy while retaining security, MicroG is private but not as secure

          Still it’s a shame that LOS can’t find a better supporter than Google

          Wdym?

            • 乇ㄥ乇¢ㄒ尺ㄖ@infosec.pub
              1·
              8 months ago

              never ever spread them as the truth.

              How did you know it’s not the truth…because I implied it wasn’t… and I don’t see it as something that couldn’t happen, people asked for MicroG support for years…

              ROMs without network support.

              I’m not a huge fan of trolling

              because they get money for doing it,

              I can tell you no Open source ROM gets funds by Google, unless if it’s a program… For example GOS received many rewards for discovering vulnerabilities in AOSP