News for hackers. Stuff that matters.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by xg15 on Friday December 09, 2016 @04:18AM (#13137633)
> What are free sites that give every user a subdomain for their profile/site/etc supposed to do?

Couldn't you include an ACME request for a new subdomain certificate into the "create account" script?

This would certainly add some complexity (especially with automatically fulfilling the "proof-of-ownership" challanges and properly renewing all the subdomain certificates) but it seems doable with less running cost than a wildcart cert subscription.

Edit: On second thought, this does leak some interesting data to the CA - such as, how many users you have, what their usernames are and how your rate of new signups is.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by garblegarble on Friday December 09, 2016 @06:11AM (#13138055)
>Couldn't you include an ACME request for a new subdomain certificate into the "create account" script?

If you're using Let's Encrypt that'd also limit you to 20 new users per week so I think you'd need a more complicated approach than that (or a different CA). Batching into groups might work but then user provisioning time increases. Wildcard certs do seem like the right way to go here, and the cost is pretty minimal

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by clinta on Friday December 09, 2016 @04:25PM (#13141983)
And that leak isn't constrained to the CA. Due to certificate transparency, that information is visible to anyone who cares to look for it.