Status of MitID app

lbschenkel

The last GOS update was pushed to my device and.... it locked itself again: "device is rooted". This is with 'OEM unlocking' disabled.

That's it, game over. Will need to get used to carry the dongle with me at all times.

Grkrz

lbschenkel do you if there is an officialy email to MitID developers?

MetropleX

It would appear having checked MtID that they are slow on updating the app:

As of April, 2022, the following combinations are supported on mobile phones and tablets:

Google Android 7, 8, 9, 10, 11 and 12 with latest version of Google Chrome, in-app (Custom tabs) or Samsung Browser 14 internet browser.
We cannot guarantee that MitID will work with other operating systems or internet browsers than the ones listed.

Having checked the Play Store listing it also targets SDK 32 (Android 12L).

Latest review:

Nobby Nobs
My phone is NOT rooted and I guarantee it, but since the latest update the MitID app tells me that the device is rooted every time I try to log in, and that logging in has been blocked for an hour. I can assure you the fault is with the app, not my phone. It's worked just fine until I needed to use it this morning, and I have changed or installed nothing new on my phone since the app actually worked. Fix it. EDIT: Now it's blocked my MitID completely. I hate this app so much.

Unless that is one of you then the issue definitely lies with the app not the OS and isnt something that can be mitigated or investigated until they officially update the SDK and advertise support for Android13.

If you can create an issue on the tracker post crash etc with the appropriate bug report, without this it will be difficult to address.

lbschenkel

Grkrz https://www.mitid.dk/en-gb/help/mitid-support/

I already filed a support case 2 days ago, but I have no false hope of it going anywhere.

lbschenkel

Some tidbits of information that I discovered by experimentation:

This latest lock-out of the app after today's GOS update happened without tripping server-side: the state is in "good standing" server-side, differently than before. But the app still refuses to work: "device rooted".
After a clean reinstall and with an un-enrolled app (*), just flipping "exploit protection compatibility mode" was enough to trigger "device rooted". Note that I tried this multiple times and it did not matter what the initial state was: the app did not complain until the switch was flipped. This makes me believe that what is happening is that the app is calculating some "stable" hash from the device state, and tripping when that hash changes because it interprets that as tampering. Maybe the recent kernel security and address randomization improvements (which go above and beyond what Google/AOSP does by default) is actually influencing some ill-implemented device hashing algorithm in MitID. New releases might be causing enough perturbation to trip it, in a way that "regular" Google/AOSP releases don't.

Once I get a new activation code I will try yet another experiment: I am going to leave 'OEM unlocking' disabled and 'Exploit protection compatibility mode' enabled and set it up again, and see if/when it trips again.

(*) Even waiting for 24h was not enough to revert the "temporary deactivation" of the authenticator once it trips; in my experience once you get "device rooted" there's no other recourse and you have to revoke it and start over.

MetropleX

Can I ask where you are all downloading the app from?

Aurora or Play Store? Another user on the Twitter Community had an issue with their bank not working when installed with former but worked with the latter.

One of the Core dev team confirms apps can see what was used to install the app and refuse to work if the source is not whitelisted or recognised.

lbschenkel

MetropleX Play Store in my case

Grkrz

MetropleX aurora

Frankdux

Aurora in mine :-)

strcat

Based on the reviews on the Play Store and discussion elsewhere, this app appears to have serious issues with Android 13 operating systems in general. It previously had issues with Android 12 operating systems before they fixed them. They're likely to start using Play Integrity attestation eventually to forbid using anything other than a Google certified OS. They simply aren't competent enough to do that yet. I wouldn't expect much unless you convince them that this is incredibly misguided and harming users.

Grkrz

strcat thank you for the feedback.

lbschenkel

FYI: I'm forwarding the response I received from MitID support:

Thank you for your e-mail.
We are aware about the issue you are experiencing, our supplier are working to solve this.
There are scheduled an update monday 7th of november, the update should fix this problem.

Grkrz

lbschenkel great job! Thanks for sharing that info.

lbschenkel

Another data point:

GOS has once again updated to latest version (TP1A.221005.002.2022110600) but this time MitID didn't break, and kept working. The combination that seems to be stable is "OEM unlock" disabled and "exploit protection compatibility mode" enabled.

This is on MitID 2.3.4, I delibetary did not update the app because I wanted to check if this problematic version would trip agan on a new GOS update.

akc3n

lbschenkel thanks for keeping everyone up dated.

Grkrz

After reinstaling the APP and setting again the user the app worked. I did a test and removed all the google play store services. MIT Id have worked, no issue ,nem id did not want to start saying app needs play services etc.
I did restarted the phone and after the reset mitid did not worked. "Device is rooted".
After installing the play services etc as it was before the app still did not worked.
I had to once more reinstall the app to make it work.
Next day the APP worked but in aurora I got google play update , could not make it update the system did not allowed I think.
I reinstalled the app and did the same as @lbschenkel . will see how long it will take till it breaks again.

Grkrz

Grkrz it did break again

lbschenkel

Grkrz just re-checked and now mine did as well. Damn.

Reaction2448

lbschenkel I am on the fence on installing GrapheneOS, as I am also a user of the MitID app.
Are the issue resolved or have you found a workaound?

lbschenkel

No workaround. The app appears to work, then it stops working and claims that the device is rooted... it might happen minutes or days/weeks later. I have resigned myself to using the dongle.

matchboxbananasynergy

lbschenkel Is there any acknowledgement from their development team as to whether that's expected or not, and if they're planning to do anything about it?

I'm asking because the topic of this app comes up from time to time, so I would like to be able to give as much current information as possible to assist them.

Reaction2448

lbschenkel
Thank you for the update. I use MitID both private and in my company, so that would be cumbersome to switch permanent to the code display unit.
Have a great weekend.

« Previous Page Next Page »