TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

When the 'S' in HTTPS also stands for shady

5 pointsby necessityabout 8 years ago

1 comment

okketabout 8 years ago
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.