Microsoft warns Authenticator will block rooted Android and jailbroken iOS, verify if your phone is affected.

  • qupada@fedia.io
    link
    fedilink
    arrow-up
    38
    ·
    24 days ago

    I can guarantee this will be a hilarious shitstorm of false positives wasting IT departments’ time, because their detection of it is massively flawed.

    At least once a month my - completely stock, and un-rooted - phone tells me I can’t use Outlook/Teams because of root. Every time, a reboot is required to resolve this. One one occasion, TWO reboots.

    Ignoring whatever reason Microsoft think they’re blocking this for, it’s going to regularly block regular users, who are not going to stand for it.

  • BurgerBaron@quokk.au
    link
    fedilink
    English
    arrow-up
    10
    ·
    24 days ago

    I don’t use my account for email anymore or use Windows very often but I just changed the two factor authenticator to Aegis. They make the text to use an alternative authenticator app tiny blue hyperlink text but you can do it confirmed.

  • Eternal192@anarchist.nexus
    link
    fedilink
    English
    arrow-up
    9
    ·
    24 days ago

    Why the fuck would you use a personal phone for work?

    Get some cheap alternative and put the authenticator on that phone and say that is your main phone.

    • OwOarchist@pawb.social
      link
      fedilink
      English
      arrow-up
      5
      ·
      24 days ago

      Better yet, if your work requires you to have Microsoft Authenticator, tell them that they need to provide you with a device capable of using it.

      Instead of spending your own money on a burner phone just for that, make your work pay for it.

    • NewNewAugustEast@lemmy.zip
      link
      fedilink
      English
      arrow-up
      4
      ·
      24 days ago

      I wont use my personal phone for anything work related except authentication. Since it sits in its own little jail, it’s fine.

      I work all over the world and remote in. I have no other work related devices or equipment.

      I look at it as a key card from the old days when I had to go into a building. I think that is a pretty trivial use case and doesn’t need them to provide a phone, and in fact I absolutely would not want a device owned by anyone else that I carried around. That is FAR worse.

      That said, this change sucks as I will now need to get around this bullshit.

  • Godort@lemmy.ca
    link
    fedilink
    English
    arrow-up
    5
    ·
    24 days ago

    How does the tool actually check for this?

    Does it just use the Play Integrety API, or does it use some kind of other attestation check?

    The need for full root privilege has fallen by the wayside assuming you can trust the OS running on the device. I dont hate this change if I can run a custom ROM that will report that the user does not have root privilege and that the OS has not been modified since boot.

  • OwOarchist@pawb.social
    link
    fedilink
    English
    arrow-up
    4
    ·
    24 days ago

    Because, obviously, you can’t be a real person if you don’t let the corpos control your device.

  • Clutter@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    ·
    22 days ago

    “Users of safe and private android versions have laughed at Microslop and their silly software”

        • marxismtomorrow@lemmy.today
          link
          fedilink
          English
          arrow-up
          5
          ·
          24 days ago

          Everyone that cares about security or privacy is working on custom android ROMs since there is no actual benefit to Apple hardware or software at this point in history. Plus you save money buying a Pixel device.

          • Hudell@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            24 days ago

            Not everyone. Depending where you live there’s no devices available that are compatible with secure custom ROMs (you might be able to deGoogle, but that’s different from being secure).

            • xep@discuss.online
              link
              fedilink
              English
              arrow-up
              2
              ·
              24 days ago

              Your security doesn’t just depend on what flavour of AOSP you decide to use. I’m assuming you’re referring to GrapheneOS, which is only compatible with Pixel devices. Your threat model is also highly relevant. Depending on who you are and what you do, you can be secure on say LineageOS, which will run on a large variety of devices.

    • hexagonwin@lemmy.today
      link
      fedilink
      English
      arrow-up
      1
      ·
      24 days ago

      yep. it’s sort of dead right now but not completely. in fact, a new bootrom exploit for Xs/11 era devices got released recently, and 11 is still getting supported on latest iOS 27.