News for hackers. Stuff that matters.
Re:Chrome 68 will mark all HTTP sites as “not secure” by TeMPOraL on Thursday February 08, 2018 @03:20PM (#16335253)
Same here.

Similarly: I have a static site (no tracking, no PIIs) that's currently hosted on a friend's VPS. HTTPS is out, because they're already using it for something else, and Apache can't know which vhost the user is requesting in time to present appropriate certificate. Maybe there's a workaround for that, but neither I nor my friend know of any, we've both already spent few hours looking, and I do not feel like spending even more time figuring out, or moving it to a dedicated VPS with its own IP.

Basically, on the one hand I'm all happy. On the other hand, I totally do not want to do the work.

And beyond that, all the extra complexity introduced everywhere that you mention, and that I also had happen to me.

Re:Chrome 68 will mark all HTTP sites as “not secure” by cmg on Thursday February 08, 2018 @03:28PM (#16335315)
If I'm understanding your issue correctly (you have two or more domains on the same IP address), then Server Name Indication (SNI) has worked for a very long time and addresses this for you: https://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI

Support is at about 97.9% globally: https://caniuse.com/#search=SNI - Effectively every browser released since 2010 plus IE 7 and 8 on Vista.

Re:Chrome 68 will mark all HTTP sites as “not secure” by TeMPOraL on Thursday February 08, 2018 @03:39PM (#16335390)
Thanks, I'll take a look at it tonight.