News for hackers. Stuff that matters.
Re:Chrome 68 will mark all HTTP sites as “not secure” by Jonnax on Friday February 09, 2018 @02:08AM (#16338478)
Why not just spin up a HAproxy container and so SSL termination on it?

Let's Encrypt also do free certificates. There's no reason to pay for one.

Re:Chrome 68 will mark all HTTP sites as “not secure” by swvjeff on Friday February 09, 2018 @02:24AM (#16338534)
A lot of these older sites are probably on old servers that LE doesn't support, making it a little less than trivial.
Re:Chrome 68 will mark all HTTP sites as “not secure” by EADGBE on Friday February 09, 2018 @10:42AM (#16340955)
This! When I was on a cheap shared and hosted solution the idea of LE was waaayyy above me.

But, I moved over everything to AWS, for the same amount of money (OK, ~$0.60 more than what I was paying before - relatively nothing), and it became a piece of cake.

That initial time commitment to the move, though, will never be recouped. I do however look at it as a career-expanding experience (fairly confident in how AWS works for projects/companies), so I got that going for it.