When Android was initially announced in 2007 by the Open Handset Alliance (headed by Google) their flagship project was billed as an "open…
  • DoucheBagMcSwag@lemmy.dbzer0.comEnglish
    35·
    1 year ago

    Treating their users like idiots and more control. Why can’t this be editable but just under Developer Mode?

    I’m just waiting for sideloading to be blocked due to “security.”

    FFS, even iOS lets you install certificate profiles

    • pimterry@lemmy.worldOPEnglish
      12·
      1 year ago

      Previously any user could modify these certs directly, even on vanilla OS images from Google themselves, without installing Magisk or any tools at all, just by writing to disk. Right now, that’s widely used and included in the setup guides for lots & lots of tools. All of that will start breaking for users when Android 14 arrives.

      I totally agree it is possible to work around this restriction, but it’s going to be significantly more complicated, and those changes will only be required because the OS used to let you read & write these files all by yourself, and now it doesn’t.

      I don’t think Android should move further in a direction where it’s impossible to directly control anything unless you install a 3rd party modification to the root daemon. That’s not a good result. These are important settings and the OS itself should allow you to control them (behind reasonable safeguards & warnings, but still).

        • deweydecibel@lemmy.worldEnglish
          4·
          1 year ago

          And then Google will punish them for figuring it out by letting apps block access. That’s the issue. If you could do all this without Google integrity checking, we wouldn’t have to worry.

      • Solar Bear@slrpnk.netEnglish
        3·
        1 year ago

        Wait, what tools, and why would they need you to modify existing certificates? That’s super sketchy.

        • pimterry@lemmy.worldOPEnglish
          8·
          1 year ago

          This is modifying system CA certs on your own device, with root access. There’s plenty of examples in the article, but most commonly you’d want to add your own CAs so that you can intercept and inspect your own network traffic. There’s a wide world of developer/researcher/reverse engineering tools that do exactly that, there’s a demo here: https://httptoolkit.com/android/

          It could plausibly be malicious, but it requires direct root access on the device, and if somebody has root access there’s already far more malicious options available to them so it’s not a meaningful threat in any sense.

    • scottywh@lemmy.worldEnglish
      3·
      1 year ago

      13 seems fine to me so far… Just upgraded to it yesterday though so maybe I’m missing something

  • InvaderDJ@lemmy.worldEnglish
    3·
    1 year ago

    Besides the listed examples from the article, what would be the impact for normal to even hobbyist root users? It seems like this is a good idea to prevent modification of legit certs and allowing certs to be updated remotely.

    As touched on above: if you’re configuring your own system CA certificates on Android right now for debugging, reverse engineering, testing or research, that option is going away in Android 14, and presumably all future versions too.