TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

When the 'S' in HTTPS also stands for shady

5 点作者 necessity大约 8 年前

1 comment

okket大约 8 年前
Let&#x27;s Encrypt does what is its purpose. Issue certificates for domain owner by verifying that they have access to that domain. It is not the purpose of the CA to check the content of the domain for illegal content. If anyone should be held accountable then it is the registrar, see<p><a href="https:&#x2F;&#x2F;www.icann.org&#x2F;resources&#x2F;pages&#x2F;abuse-2014-01-29-en" rel="nofollow">https:&#x2F;&#x2F;www.icann.org&#x2F;resources&#x2F;pages&#x2F;abuse-2014-01-29-en</a><p>That said there are some ways to mitigate this problem:<p>a) The domain owner can publish a &#x27;CAA&#x27; record(s) in their DNS zone, which list Certificate Authorities that should be allowed to issue certificates. If Let&#x27;s Encrypt sees this and it is not in the list, they will not issue an certificate.<p>b) Certificate Transparency: Let&#x27;s Encrypt and other CAs inform neutral CT server about newly issued certificates. An organisation that is often targeted by abuse (e.g. PayPal) can monitor these and react appropriately if they detect malicious behaviour.