Google shifting to “upstream first” Linux kernel approach for Android features

Re:Google shifting to “upstream first” Linux kernel approach... by SXX on Thursday September 23, 2021 @08:13AM (#28628073)

> Googles own devices not only allow you to unlock the bootloader, but to relock it with your own signing keys.

And does it let you pass SafetyNet and run most of the apps. AFAIK it's not so re-lockable bootloader is useless.

[ Parent | on HN ]

Re:Google shifting to “upstream first” Linux kernel approach... by NikolaeVarius on Thursday September 23, 2021 @09:40AM (#28628975)

I have a unlocked booloader and I bypass SafeyNet just fine.

[ Parent | on HN ]

Re:Google shifting to “upstream first” Linux kernel approach... by SXX on Thursday September 23, 2021 @02:55PM (#28633569)

For now. Once SafetyNet start to require hardware attestation you won't be able to bypass it with Magisk.

[ Parent | on HN ]

Re:Google shifting to “upstream first” Linux kernel approach... by dmm on Thursday September 23, 2021 @08:48AM (#28628352)

I use a pixel phone with my own signing keys and I find it very useful. I can live without SafetyNet, whatever that is.

[ Parent | on HN ]

Re:Google shifting to “upstream first” Linux kernel approach... by krzyk on Thursday September 23, 2021 @09:07AM (#28628537)

It basically allows you running most banking apps (and anything that is related to money).

[ Parent | on HN ]

Re:Google shifting to “upstream first” Linux kernel approach... by bilkow on Thursday September 23, 2021 @01:04PM (#28631972)

Where I live, both of my banking apps work without SafetyNet and even Google Play Services. I have missed one or another app for having no Play Services, but nothing too important and it's offset by having the option to block all internet connection for other apps.

[ Parent | on HN ]