Early Impacts of Let's Encrypt
tacticalsecret.com
Early Impacts of Let's Encrypt
1–10 of 98 posts
Re: Early Impacts of Let's Encrypt
#2Re: Early Impacts of Let's Encrypt
#3There certainly seems to have been pent-up demand.
Re: Early Impacts of Let's Encrypt
#4> In the first quarter of its' operation then, Let's Encrypt has far and away been used more to secure previously-unsecured (or at least untrusted) websites than simply as a cost-savings measure.
Re: Early Impacts of Let's Encrypt
#5Re: Early Impacts of Let's Encrypt
#6Re: Early Impacts of Let's Encrypt
#7I've used them a bunch. We host a lot of internal-facing utilities that are low-profile, but occasionally hosting sensitive data. In the past I couldn't convince managers to spend money on certs even if the cost of someone stumbling on these sites could be very high and certs are cheap. Now I don't even have to ask.
Re: Early Impacts of Let's Encrypt
#8I've used them a bunch. We host a lot of internal-facing utilities that are low-profile, but occasionally hosting sensitive data. In the past I couldn't convince managers to spend money on certs even if the cost of someone stumbling on these sites could be very high and certs are cheap. Now I don't even have to ask.
Re: Early Impacts of Let's Encrypt
#9Re: Early Impacts of Let's Encrypt
#10Does anyone know where one can get a free wildcard certificate? Need it for development and foo/bar/baz/biff.example.com change names regularly (they include the hash of the code commit) so I would like to get a *.dev.example.com wildcard cert. (one that won't give warnings that scare the business types who are testing the code, and won't understand what self-signed means.)