Firefox and Chrome start calling HTTP connections insecure Options

[Christian J]

https://arstechnica.com/information-technol...tions-insecure/

The non-secure labelling will occur on pages delivered over HTTP that include forms. Specifically, pages that include password fields, and in Chrome, credit card fields, will put warnings in the address bar to explicitly indicate that the connection is not secure.

My guess is this will primarily affect login pages on web forums (including this one). Most online payment and banking sites should hopefully use HTTPS already. Don't know about minor webmail providers.

A future version of Firefox will include a warning immediately adjacent to the password box itself whenever the page is delivered over HTTP, and Mozilla plans to use the struck through padlock icon for every HTTP page. Similarly, Google intends to eventually include the "Not secure" message in the address bar for all pages delivered over HTTP, whether they contain passwords or not.

Of course if the majority of normal HTTP sites are labeled as "insecure", the warning will soon be ignored.

Some more opinions on the matter:
https://www.troyhunt.com/heres-how-broken-t...default-future/
https://konklone.com/post/were-deprecating-...oing-to-be-okay
https://medium.com/@b_k/https-the-end-of-an-era-c106acded474