As you know, he's aware and thanked @Displax for his fix / PR... And he does clearly want to improve the solution and scope the methodWhy kdragon doesn't update it, or there are no good solution for that?
https://github.com/kdrag0n/safetynet-fix/pull/207#issuecomment-1195452147to Play Integrity code by identifying methods it calls near the beginning and end of integrity checks, and adding hooks to set and restore the fingerprint ...
He has already suggested an idea for adding an end hook, but said:
https://github.com/kdrag0n/safetynet-fix/pull/207#issuecomment-1200437447Of course, this is all theoretical as it depends on the exact order of steps in the integrity checking process. Worst case scenario, we could just sleep for 1 second or so and revert the fingerprint change in a background thread. Not sure when I'll have time to look into it myself, but feel free to try implementing this idea: ...
- So it seems he's in no rush himself, and he's happy for other Devs to test / contribute (although none appear to have tried adding hooks etc yet)...
I guess he'll do more on this PR as time allows... If other Dev's haven't had time to test even proposed
idea, then he may think 'why should I rush?'... He probably has a ton of more important maintenance on his plethora of apps, utilities, Proton ROM / kernel builds, etc to do...thread(daemon = true) {
- Set the fingerprint in the key attestation hook
- Spawn a thread to revert it after 3 seconds:
Thread.sleep(3000)
/* revert */
}
Meanwhile, @Displax solution seems a pretty good one to tide us over, for most devices... PW