4 ms·
How about we put a distinctive icon in the trusted zones, which the renderer won't allow under any circumstances in the untrusted area. Also with a buffer so n
by qume 10y ago
How about we put a distinctive icon in the trusted zones, which the renderer won't allow under any circumstances in the untrusted area.
Also with a buffer so nothing too similar is allowed, or perhaps a warning comes up if something is close.
I vote for something like the chrome dinosaur.
- deathanatos 10y agoIsn't this essentially the lock icon, today? What is "trusted"? We get the lock icon if a valid TLS connection is formed; if you want a more secure connection, you can get EV certificates. We could do away with the lock icon and only show a broken lock if not on TLS, and only show something that looks secure on EV certs, (which seems to be where browsers are headed.) A simple valid TLS connection getting the lock icon is problematic when people are using DNS names that are close-but-not-quite to things like paypal.com. And we want TLS certs to be issued automagically ala Let's Encrypt and such, so it's easy, unfortunately, to get a cert for paypal-not-quite.com. Such is the difference in "secure connection" and "a secure connection to a party you trust."
- qume 10y agoPretty much - except the rending engine won't let that block of pixels allow to hit the framebuffer
- laughinghan 10y ago> How about we put a distinctive icon in the trusted zones, which the renderer won't allow under any circumstances in the untrusted area. So in the blogpost announcing this distinctive icon, what does the screenshot look like?