Re:Chrome 56 will mark HTTP pages with password fields as no...
by lucideer on Sunday January 22, 2017 @05:16PM
(#13457938)
That's the point. SSL/TLS is a standard feature nowadays. If you're a web host and you don't support certs or charge some unreasonable fee for adding them (and I'm well aware there are far too many of these out there), then you need to be losing business fast. Your customers should be moving to better competitors. This measure just accelerates this process.
[ Parent
| on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no...
by johndoe4589 on Monday January 23, 2017 @09:31AM
(#13462350)
True, it's just the transition atm is a bit painful.
My host is asking ~80 USD for multi domain SSL. It's not that bad, but they don't support Let's Encrypt yet afaik. Are they aware of this and trying to cash in on people who don't want the hassle of moving their sites?
On the other hand, if I buy there is none of that "auto renew" business...