Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and CSS Position: Sticky
This is too soon if Google goes forward with the red exclamation point &quot;insecure&quot; flag before there is a free solution for wildcard certificates.<p>What are free sites that give every user a subdomain for their profile&#x2F;site&#x2F;etc supposed to do? There are many open source multi-user site platforms that follow this pattern, and all of these platforms now effectively have a huge monetary subscription fee associated with them due to the fact that you now need to purchase a wildcard certificate in order to not scare away users.<p>There is no free wildcard SSL certificate service, so Google is essentially forcing you to pay money to not scare users away from your site.<p>I am all for this change eventually happening, but not until <i>all</i> DV SSL use cases are covered by free services. Until then, this change is inappropriate.<p>If Google wants to punish sites that can&#x27;t afford or won&#x27;t pay for expensive wildcard certificates, then they should offer a solution of their own (like their own ACME CA that supports provisioning wildcard certs).