RoundcatThe state of the internet 2023
#enshitification #twitter #reddit #google #fediverse #meta #facebook #youtube #elon #lemmy #mastodon
Zinggi57I think a lot of people here don’t understand the danger of this fully and dismiss it with “Just use Firefox, problem solved”.
Unfortunately, once this becomes widely available, that is once Chrome ships it, websites will start to use it.
Maybe Amazon will just not sell to you anymore when you’re browsing with Firefox?
Maybe YouTube wont serve any videos if you’re using Linux?
Your bank will certainly implement this and only allow Windows 11 with Edge or some shit like that.
Once this is implemented, we will all suffer, even if we’re using better alternatives right now.
Ember UshiYour bank will certainly implement this
My brother in Christ, it was 2020 before my bank supported passwords longer than 8 characters. We have 30 or 40 years before we need to worry about the banks.
Da_BoomHave you ever rooted an android phone?
The google SafteyNet Attestation is the precursor to browser DRM. It’s essentially phone DRM.
There are many banks that have apps that require you to pass at least the basic level attestation, if not the CTS profile matching that fails the moment you modify any system level resources, even the bootloader
luckily you can force disable CTS so it falls back on the basic level, for most apps at least. You will never have access to Google or Samsung pay though, as it actually knows your phone model should support CTS and will autofail if it no longer reports that it does.
Alongside that apps like Pokemon GO and Netflix also require at least basic attestation to function - demonstrating the DRM and anticheat capabilities of such a system.
CumBrothgithub.com/…/MagiskHidePropsConf
This can help you pass CTS. It worked for me. Funny thing is, I don’t even remember which apps I did it for. Whatever it was, I ended up not using it after all the trouble. As for my banking apps, they only care about root, so Magisk’s denylist does the job.
Nah, I’m still running a stock ROM on a pixel 3a. Looking at this guide, it looks like this tool is dead. So unless it works on android 12, I can’t use it.
Enabling strict denylist actually causes my phone to break, it will randomly cause my phone to freeze up, and fail to load on phone unlock to the point I have to go into safe boot to disable my Magisk modules, only then will it boot correctly. - maybe I’m denying the wrong system apps for strict mode to work. I have still added apps to the denylist, however.
Im currently using universal Safetynet Fix to pass basic Attestation, and the only thing that fails to work is google wallets “tap to pay” feature. Which doesn’t matter as my NFC reader is broken in any case.
Oh, I didn’t notice it’s dead. I just had it bookmarked because I remember spending a lot of time trying all sorts of workarounds before it and none of them ever worked (for CTS).
I used this for Android 11; there’s a good chance it’ll still work for that version. But like I said, I ended up not needing it anyway - my phone doesn’t even have NFC! I think I mostly just did it as a FU to Google rather than for actual utility. :D
Just thought it worth mentioning that there are/were workarounds to it. Don’t know how things are now on Android 12 and 13.