There's been a lot of concern recently about the Web Environment Integrity proposal, developed by a selection of authors from Google, and…
Apple has deployed a system called Private Access Tokens that allows web servers to verify if a device is legitimate before granting access. This works by having the browser request a signed token from Apple proving the device is approved. While this currently has limited impact due to Safari's market share, there are concerns that attestation systems restrict competition, user control, and innovation by only approving certain devices and software. Attestation could lead to approved providers tightening rules over time, blocking modified operating systems and browsers. While proponents argue for holdbacks to limit blocking, business pressures may make that infeasible and Google's existing attestation does not do holdbacks. Fundamentally, attestation is seen as anti-competitive by potentially blocking competition between browsers and operating systems on the web.
If a website doesn't want me to see their shit, then I guess i won't see their shit. I already have some sites that don't work because of my aggressive use of lists on my pihole, in addition to the usual browser plugins. If a site doesn't work now, I just move on. I don't give a shit about any site enough to put up with this type of bullshit.
What if it's your bank's website? Or email provider? Or literally anything else you actually have to choose and can't pick? "It's okay because I don't think it affects me / I can ignore it" is always a bad reason to allow a bad thing happen.
Use the phone app or, oh I don't know, fucking go in?
Or email provider?
Change your email provider? Run your own email like people should?
Or literally anything else you actually have to choose and can’t pick? “It’s okay because I don’t think it affects me / I can ignore it” is always a bad reason to allow a bad thing happen.
When the fuck did I say that? I said I'm not going to deal with it. I won't. I'll work around it, or change the company I'm using. That is what you need to do to stop this type of shit.
EDIT: Holy crap some people are stupid. Register a domain <whatever>.com. You don't even need to host a website. Now configure the register to point to your mail server. I've done this for decades, across different carriers. And I haven't lost my email.
Or don't do any of that and happily bend over and take whatever Apple or Google force on you. You do you.
Every time I've ever looked into it or read anything on the topic it's been like "do not do this. I lost my father, my children, two wives, and all my Pokemon cards in this endeavour, but in case you don't want to listen, here's how I partially successfully hosted my own email server for three months..."
It's not that bad but definitely not a solution for everyone. And you probably still don't want to do it for your primary mail unless you're otherwise extremely well versed in doing so, up to and including running multiple servers for redundancy.
Not exactly. Having a running software is one thing, not having your emails be blocked by everyone because you're not a trusted host is another. That another is a deal breaker and a huge pain in the ass, even though it helps fighting spam
And the emails from your custom server will be rejected and/or marked as spam by every major corporation, and you will spend countless days writing appeals and appeal rejects
Cannot confirm, somewhat. Setting it up so you don't get blocked is rather easy, figuring out how to do that correctly is a bit of a pain though (I only managed to correctly set things up once I started using Mailcow and their built in DNS check tool)
The domain still lands on some blacklists but that is down to one ISP blanket banning any mail servers in the IP block my ISP rotates my IP through.
Unfortunately google is aggressive at spam filtering. For example when I signed up for bookwormstory.social the confirmation mail was sent straight to spam automatically (I had to fish it out and mark it not as spam) 😔
It's pretty shitty for a company to force someone to use a phone app or go to something as vital as a bank just because they won't let the customer access the website. And there are plenty of reasons why someone wouldn't be able to go to the bank in person every time they needed to, or at least it'd be extremely inconvenient to (especially for small things like checking your balance or transactions). Not everyone has a phone either.
Change your email provider? Run your own email like people should?
I've never deleted my email before but I'm pretty sure that means losing access to your entire inbox that you've likely had for years and having to update your contacts, the emails for all the accounts you have under it, etc. And being blocked from the website means you won't be able to do any of those things through the official website. Does device atteststion prevent you from accessing your email through third party clients?
How do you "fucking go in" to an online bank? And why are you being so aggressive about a simple question? Getting tired of people still acting like redditors here.
And how the fuck is a phone app an alternative for avoiding attestation??? A phone app is inherently attested by being distributed through the app store.
On a rooted phone, they can still fail attestation, apparently. That's why Magisk Hide (or whatever it's called) became a thing, to hide that the device is rooted. Google Pay also apparently needs Magisk Hide to function.
I don't trust my phone to store my payment details, so I don't care about Google Pay, and my bank's app works fine while rooted, so I don't have any personal experience with it, just what I've seen in every single root guide I've used in at least the last 4 years (if not longer; I don't remember how I rooted my previous phone.)
Yeah, joke's on the commenter; Google had had device attestation for phones for ages now and it's also terrible. Many apps will outright refuse to work if you have a non-typical phone (rooted, some obscure hardware or custom OS).
This is true. However, I don't see this happening as the website/browser isn't really the problem with online banking, it's more often the user.
On another note, how about no access at all, because this is a freaking huge attack surface for (D)DOS. Imagine you just invalidate signatures of all traffic to and from an attestation service. You could almost stop countries from functioning. That's a serious vulnerability which we can easily do without.
I rarely do, but when I do it's for something a bit specific, like ordering/depositing foreign currency (for travel) or depositing large checks that exceed the online deposit limit (which again is extremely rare). For everything else, it's online only, especially since every time I go in, there's only one teller working and the line is super long.
Jokes on you. It refuses to work as my phone configuration is not approved by our corporate overlords.
And yeah, obviously you can go to the bank at any moment, there are no times whatsoever when you need to do something right now, without lets say leaving the cash register at the shop
And that's not even getting into how banks worldwide have been cutting down on staff numbers for years, and directing people to just their apps instead.
To see how your approach works, try using the Internet with Javascript turned off for reading text. You will realize you can't organize your life nowadays without bowing to what websites do technically.