4 ms·
it's not insecure if you trust the company. should google block everypass.com just because it have your banking acount password? if i'm on a slow connection a
by gcb0 14y ago
it's not insecure if you trust the company.
should google block everypass.com just because it have your banking acount password?
if i'm on a slow connection and have to use this browser to compress my connection to my bank, i will decide if i trust the browser to do so.
I just think nokia should have been even more open about this. and probably gave me an option on the browser. In that they sinned.
- esrauch 14y agoI don't see how everypass.com is relevant. In this case when I go to https://www.google.com https://www.google.com I expect that any traffic can only be seen by Google, the entire reason I typed "https" was specifically so that it was only a conversation between me and the site that I'm connecting to and no other middle men. It is of no consequence what company it is; it would be inappropriate for Google to be seeing my encrypted traffic to hotmail and it would be inappropriate for Microsoft to see my encrypted traffic to gmail. Google continuing to serve traffic under those conditions is misleading and Google (or any other site that supports https) shouldn't allow it.