Hulk

  • Feb 7, 2024
  • Joined Jun 10, 2022
  • In Block malicious signaling messages?

    Titan_M2

    Having skimmed through your article it sounds to me like the problem is that all networks are insecure by design and it is up to the lawmakers, carriers and other operators to improve their security. GrapheneOS already assumes all networks are bad and have implemented all effective measures against that it can, including, as per @Hulk's bear-simile, the issues in the article.

    And as for targeted malicious signaling messages, doesn't the last paragraph cover that specifically?

    Receiving a silent SMS is not a good indicator of being targeted by your cell carrier, police or government because anyone on the cell network can send them including yourself. Cellular triangulation will happen regardless of whether or not SMS texts are being sent or received by the phone. Even if an SMS did serve a useful purpose for tracking, a silent SMS would be little different than receiving unsolicited spam. In fact, sending spam would be stealthier since it wouldn't trigger alerts for silent SMS but rather would be ignored with the rest of the spam. Regardless, sending texts or other data is not required or particularly useful to track devices connected to a network for an adversary with the appropriate access.

    Airplane mode is the only way to avoid the cellular network tracking your device and works correctly on the devices we support.

      • In General usage: short how-to's and quick tips

        @Hulk, what are the benefits of setting an eSIM in Stock Android versus setting it up in GOS with sandbox Google Play and them removing Google Play once it is set?

      • In Gesture bar in landscape mode

        sev

        Regards the white bar please see: https://discuss.grapheneos.org/d/608-how-to-remove-bottom-white-bar/7

        In reference to root methods such as Magisk being used on GrapheneOS:

        If you unlock your bootloader and root your device you are then NOT running GrapheneOS which will be confirmed by Auditor when you run it afterwards. As such the discussion would no longer be appropriate for the GrapheneOS Discussion Forum as you are no longer discussing GrapheneOS.

        @flawedworld It would be a violation of the security model and we will never support root
        Source: [Matrix]

        @Hulk GrapheneOS with root is not GrapheneOS
        Source: [Matrix]

        @TommyTran732 No point in using GrapheneOS if you are rooting. You are cripling your security with that.
        Source: [Matrix]

        @june:grapheneos.org we also are not exposing root support in any way. they can compile the OS themselves with root support or leave the bootloader unlocked with a patched boot image knowing they have ruined the security and privacy of GrapheneOS.
        Source: [Matrix]

        @akc3n Root destroys the Android Security Model.
        Source: [Matrix]

        @matchboxbananasynergy In a way, even if it's possible, a rooted GrapheneOS installation isn't really GrapheneOS anymore :)
        Source: [Matrix]

        As this is the GrapheneOS Discussion Forum further discussion surrounding such things would not be appropriate.

        • In Alternative keyboard other than GBoard

          Cigurd having looked into Japanese keyboards matching your requirements it is indeed highly likely that GBoard is requiring a connection to the cloud to determine your kanji/katakana alternatives.

          The only thing I can suggest is to try leaving GBoard with network without inputting anything, adding the language packs of your choice and leaving it with internet for 5-10 minutes depending on connection speed. Once done, disable network and try to type as you would and let me know if the kanji/katakana appears as it should.

          I can also confirm with what @Hulk has reiterated nobody has altered or censored anything you have previously posted, Everything still reads as per your quote.

            • In call recording patch for aosp dialer

              abcZ Your choice to hide basically the ONLY possible option for this is not appropriate.

              I completely appreciated your emphasis on it being a downside which is why I added the response emphasising what the posts were about so people could continue their own research elsewhere, there are numerous places to discuss this option across the web, this forum however is the:

              GrapheneOS Discussion Forum

              If you unlock your bootloader and root your device you are then NOT running GrapheneOS which will be confirmed by Auditor when you run it afterwards. As such the discussion would no longer be appropriate for the GrapheneOS Discussion Forum as you are no longer discussing GrapheneOS.

              @flawedworld It would be a violation of the security model and we will never support root
              Source: [Matrix]

              @Hulk GrapheneOS with root is not GrapheneOS
              Source: [Matrix]

              @TommyTran732 No point in using GrapheneOS if you are rooting. You are cripling your security with that.
              Source: [Matrix]

              @june:grapheneos.org we also are not exposing root support in any way. they can compile the OS themselves with root support or leave the bootloader unlocked with a patched boot image knowing they have ruined the security and privacy of GrapheneOS.
              Source: [Matrix]

              @akc3n Root destroys the Android Security Model.
              Source: [Matrix]

              @matchboxbananasynergy In a way, even if it's possible, a rooted GrapheneOS installation isn't really GrapheneOS anymore :)
              Source: [Matrix]

              • In Thinking about installing GraphineOS on my Pixel 6

                fomijafi I hear you and get you, my employer only 'permits' Microsoft Authenticator, yet Aegis is what I use. Most cases the people pushing one or the other don't have a clue. Even while using Aegis I asked our IT guys if others could be used. They said no (Thanks @Hulk 😜). There is a reason I don't always trust 'professionals' lol

                  • In Pixel 5 no audio when phone call is answered using dialer

                    Hey @Hulk thanks for the reply.

                    Double checked this mic access issue, and it doesn't seem to be the problem since the Mic Access is enabled and I don't turn it off. Also this happens with outgoing calls, so the phone is already unlocked. I use WiFi calling, but I try with WiFi off when I make calls and it still doesn't work. And again, the issue happens like 80% of the time, not always. :T