210 karma · joined October 7, 2021
Done.
We also all know that they have the best dark patterns and just-not-too-sketchy business practices. Everybody at Adobe knows too.
Good luck with the fight.
Firefox makes you fix the root problem.
Encrypted transit but you might be talking with the hacker on the other end == worthless.
And with plaintext transit you cannot prove integrity during transit AND also not prove talking with the proper endpoint.
In short: Browser really is warning you that something is fishy. Don’t shoot the messenger.
1: Suggested package: sillier.
But that also is proof for the abstract! By having this image, MS preselects on engineers with lower ethical standards.
It’s not validating reused codes or tokens from an application owned by attacker.
Just ask the author for a proper onetime invoice. Maybe not all OSS authors will do it, but I woud be happy to make a quick PDF for a nice buck. :)
Now the real reason that doesn’t happen more often: Our financial departments and/or bureaucracy inside the org are actively hindering frivolous acts as being nice to others.
The header at media queries says “Fingerprinting resistance”. Some data point like screenwidth doesn’t immediately disclose you identity. But having a few data points helps with fingerprinting.
I’ve had this too. It felt weird, but isn’t that bad: You sign just the same before a second attempt, so might as well continue. And the upside of having to do this ad hoc is that it’ll help on future card usage.
But the following likeliness check is hilarious of course. :)
Source: From Europe. Europe already might be in the same ballpark + I don’t forget about other continents.
In a secure hash function, all output bits are without bias. So all combinations exist.