[kxrm]

I agree that not everything needs to be encrypted, but unfortunately a lot of people who browse the web are concerned when the browser complains that something is not secure.

From the browser maker's side, how does a browser know whether something should or should not be secured? They have clearly taken a more aggressive approach to inform users what is going on within the underlying protocol. While I do agree that not everything needs to be encrypted, I also agree that the user should know what is or is not happening under the hood.

[zakki]

I guess the warning should be “not encrypted “. Being encrypted doesn’t mean being secure (as there is a way to overcome the encryption).

[sodality2]

Explain how this encryption can be “overcome”..?