mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
translated
This commit is contained in:
parent
fecb3b9cfa
commit
eebf476053
@ -1,36 +0,0 @@
|
||||
translating---geekpi
|
||||
|
||||
Wildcard Certificates Coming January 2018
|
||||
============================================================
|
||||
|
||||
|
||||
Let’s Encrypt will begin issuing wildcard certificates in January of 2018\. Wildcard certificates are a commonly requested feature and we understand that there are some use cases where they make HTTPS deployment easier. Our hope is that offering wildcards will help to accelerate the Web’s progress towards 100% HTTPS.
|
||||
|
||||
Let’s Encrypt is currently securing 47 million domains via our fully automated DV certificate issuance and management API. This has contributed heavily to the Web going from 40% to 58% encrypted page loads since Let’s Encrypt’s service became available in December 2015\. If you’re excited about wildcard availability and our mission to get to a 100% encrypted Web, we ask that you contribute to our [summer fundraising campaign][1].
|
||||
|
||||
A wildcard certificate can secure any number of subdomains of a base domain (e.g. *.example.com). This allows administrators to use a single certificate and key pair for a domain and all of its subdomains, which can make HTTPS deployment significantly easier.
|
||||
|
||||
Wildcard certificates will be offered free of charge via our [upcoming ACME v2 API endpoint][2]. We will initially only support base domain validation via DNS for wildcard certificates, but may explore additional validation options over time. We encourage people to ask any questions they might have about wildcard certificate support on our [community forums][3].
|
||||
|
||||
We decided to announce this exciting development during our summer fundraising campaign because we are a nonprofit that exists thanks to the generous support of the community that uses our services. If you’d like to support a more secure and privacy-respecting Web, [donate today][4]!
|
||||
|
||||
We’d like to thank our [community][5] and our [sponsors][6] for making everything we’ve done possible. If your company or organization is able to sponsor Let’s Encrypt please email us at [sponsor@letsencrypt.org][7].
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html
|
||||
|
||||
作者:[Josh Aas ][a]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html
|
||||
[1]:https://letsencrypt.org/donate/
|
||||
[2]:https://letsencrypt.org/2017/06/14/acme-v2-api.html
|
||||
[3]:https://community.letsencrypt.org/
|
||||
[4]:https://letsencrypt.org/donate/
|
||||
[5]:https://letsencrypt.org/getinvolved/
|
||||
[6]:https://letsencrypt.org/sponsors/
|
||||
[7]:mailto:sponsor@letsencrypt.org
|
@ -0,0 +1,34 @@
|
||||
2018 年 1 月发布通配证书
|
||||
============================================================
|
||||
|
||||
|
||||
Let’s Encrypt 将于 2018 年 1 月开始发放通配证书。通配证书是一个经常需要的功能,并且我们知道有一些使 HTTPS 部署更简单情况。我们希望提供通配证书有助于加速网络向 100% HTTPS 的进展。
|
||||
|
||||
Let’s Encrypt 目前通过我们的全自动 DV 证书颁发和管理 API 保护了 4700 万个域名。自从 Let's Encrypt 的服务于 2015 年 12 月发布以来,它已经大大地将加密网页的数量从 40% 提高到 58%。如果你对通配证书的可用性以及我们达成 100% 的加密网页的使命感兴趣,我们请求你为我们的[夏季筹款活动][1]做出贡献。
|
||||
|
||||
通配符证书可以保护基本域的任何数量的子域名(例如 *.example.com)。这使得管理员可以为一个域及其所有子域使用单个证书和密钥对,这可以使 HTTPS 部署更加容易。
|
||||
|
||||
通配符证书将通过我们[即将发布的 ACME v2 API 终端][2]免费提供。我们最初只支持通过 DNS 进行通配符证书的基础域验证,但是随着时间的推移可能会探索更多的验证方式。我们鼓励人们在我们的[社区论坛][3]上提出任何关于通配证书支持的问题。
|
||||
|
||||
我们决定在夏季筹款活动中宣布这一令人兴奋的进展,因为我们是一个非营利组织,这要感谢使用我们服务的社区的慷慨支持。如果你想支持一个更安全和保密的网络,[现在捐赠吧][4]!
|
||||
|
||||
我们要感谢我们的[社区][5]和我们的[赞助者][6],使我们所做的一切成为可能。如果你的公司或组织能够赞助 Let's Encrypt,请发送电子邮件至 [sponsor@letsencrypt.org][7]。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html
|
||||
|
||||
作者:[Josh Aas ][a]
|
||||
译者:[geekpi](https://github.com/geekpi)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html
|
||||
[1]:https://letsencrypt.org/donate/
|
||||
[2]:https://letsencrypt.org/2017/06/14/acme-v2-api.html
|
||||
[3]:https://community.letsencrypt.org/
|
||||
[4]:https://letsencrypt.org/donate/
|
||||
[5]:https://letsencrypt.org/getinvolved/
|
||||
[6]:https://letsencrypt.org/sponsors/
|
||||
[7]:mailto:sponsor@letsencrypt.org
|
Loading…
Reference in New Issue
Block a user