This could turn out to be a huge annoyance for full screen apps.
Imagine this stuff popping up on a housemaid while she’s watching a cooking video.
The need to store trusted keys would mandate the need to interact with the system and upload the list after every session from a different device. One PUT
per login (if a new public key is added).
Which makes it possible for 2 users to go to g00gle.safe and end up on different sites.
google.safe
would probably never become a target (because they’ll make a crapload of money), but personally I would attack sites like savethechildren.safe
and such small-timers - you could bust them for peanuts.
One would never know how much he has to pay if the method of calculation was simple.
A sophisticated formula could be created but where would it run?
It’s not the “big brands”, it s everyone.
So an app vendor hardcodes his app to get some stuff from secure.safe, and a week later secure.safe gets bought by a hacker syndicate.
Ugh, as if there already aren’t enough ways to end up on a wrong site!