News for hackers. Stuff that matters.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by Tushon on Friday December 09, 2016 @12:15AM (#13136830)
Zendesk, for example, has a Let's Encrypt-based system for all those <account>.zendesk.com pages. While it wouldn't be trivial to set it up, it is free and the information is out there if the admins of those sites want to make it possible.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by kuschku on Friday December 09, 2016 @05:14AM (#13137852)
Not everyone can get whitelisted from the domain creation limits of LE.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by Ajedi32 on Friday December 09, 2016 @12:57PM (#13140378)
Unless you're creating [more than 20 new subdomains a week][1], you're not gonna hit that limit anyway. You can increase that figure to around 2,000 new subdomains a week if you're willing to include multiple subdomains per certificate; that should be more than enough for all but the largest of sites.

And even if you do need more:

> If you are a large hosting provider or organization working on a Let’s Encrypt integration, we have a rate limiting form that can be used to request a higher rate limit.

[1]: https://letsencrypt.org/docs/rate-limits/

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by kuschku on Friday December 09, 2016 @01:11PM (#13140498)
If you want to have a signup process that takes less than 9 hours, you have a max of 20 new subdomains a week.

20 users signing up a week - likely with a retention of a few percent - is not a "large hosting provider".

You might have a few hundred users max, and already will be far over the rate limits.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by Ajedi32 on Friday December 09, 2016 @01:31PM (#13140672)
Just start them off with HTTP and transparently upgrade to HTTPS after 9 hours. And if you're only retaining a small percentage of users who sign up, you can stretch that limit even further by only upgrading the users who you retain.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by Sephr on Friday December 09, 2016 @04:12PM (#13141898)
This isn't possible in a properly deployed HTTPS site, since it would already have an HSTS header with includeSubdomains.