Let’s Encrypt to Offer Wildcard Certificates in 2018

Certificate authority Let’s Encrypt said this week it will begin offering wildcard certificates in 2018.

Wildcard certificates are public key certificates that can be used with multiple subdomains of a domain. The certificates are traditionally viewed as less expensive and more convenient by webmasters.

Josh Aas, executive director for the Internet Security Research Group, the nonprofit corporation behind Let’s Encrypt, announced the news via a blog entry Thursday.

Aas says he hopes the effort will make HTTPS deployment easier for Let’s Encrypt users and help “accelerate the Web’s progress towards 100% HTTPS,” long a goal of the initiative.

The CA said it would begin offering wildcard certificates to users beginning in January of next year. It will only support base domain validation via DNS for wildcard certificates at first but could add additional validation options over time, Aas said.

The certificates will be offered for free via the CA’s forthcoming ACME v2 API endpoint. Announced in June, the IETF-standardized protocol is slated to launch around the same time Let’s Encrypt plans to begin offering wildcard certs.

The protocol, a medium for subscribers to acquire and manage certificates, will build off the CA’s ACME v1 protocol API but won’t replace it just yet.

“Once we’re confident that we can predict an appropriate end-of-life date for our ACME v1 API endpoint we’ll announce one,” Aas said last month.

The news comes a week after the CA announced it had issued more than 100,000,000 certificates.

Aas and Let’s Encrypt still have a long way to go until 100 percent of web pages are loaded by HTTPS but the CA has made some admirable strides over the past year and a half since the CA’s inception. When the Let’s Encrypt first entered public beta in December 2015 less than 40 percent of page loads used HTTPS. Since then, a span of 19 months, HTTPS loads have jumped 18 percent to nearly 58 percent.

from Threatpost – English – Global – thr… http://bit.ly/2tRJgBL
via IFTTT

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s