词条 | DNS Certification Authority Authorization |
释义 |
| status = Proposed Standard | first_published = {{Start date|2010|10|18}} | version = {{IETF RFC|6844}} | version_date = January 2013 | organization = IETF | authors = {{Plainlist|
}} | abbreviation = CAA }}{{Internet security protocols}} DNS Certification Authority Authorization (CAA) is an Internet security policy mechanism which allows domain name holders to indicate to certificate authorities whether they are authorized to issue digital certificates for a particular domain name. It does this by means of a new "CAA" Domain Name System (DNS) resource record. It was drafted by computer scientists Phillip Hallam-Baker and Rob Stradling in response to increasing concerns about the security of publicly trusted certificate authorities. It is an Internet Engineering Task Force (IETF) proposed standard. BackgroundA series of incorrectly issued certificates from 2001 onwards[1][2] damaged trust in publicly trusted certificate authorities,[3] and accelerated work on various security mechanisms, including Certificate Transparency to track mis-issuance, HTTP Public Key Pinning and DANE to block mis-issued certificates on the client-side, and CAA to block mis-issuance on the certificate authority side.[4] The first draft of CAA was written by Phillip Hallam-Baker and Rob Stradling, and submitted as an IETF Internet Draft in October 2010.[4] This was progressively improved by the PKIX Working Group,[5] and submitted to the IESG as {{IETF RFC|6844}}, a Proposed Standard, in January 2013.[6] CA/Browser Forum discussion began shortly afterward,[4] and in March 2017 they voted in favor of making CAA implementation mandatory for all certificate authorities by September 2017.[7][8] At least one certificate authority, Comodo, failed to implement CAA before the deadline.[9] A 2017 study by the Technical University of Munich found many instances where certificate authorities failed to correctly implement some part of the standard.[10] {{As of|2018|June}}, Qualys reports that still, only 3.4% of the 150,000 most popular TLS-supporting websites use CAA records.[11]RecordCertificate authorities implementing CAA perform a DNS lookup for CAA resource records, and if any are found, ensure that they are listed as an authorized party before issuing a digital certificate.[6] Each CAA resource record consists of the following components, separated by whitespace:[6]
; issue : This property authorizes the holder of the domain specified in associated property value to issue certificates for the domain for which the property is published. ; issuewild :This property acts like issue but only authorizes the issuance of wildcard certificates, and takes precedence over the issue property for wildcard certificate requests. ; iodef : This property specifies a method for certificate authorities to report invalid certificate requests to the domain name holder using the Incident Object Description Exchange Format. {{As of|2018}}, not all certificate authorities support this tag, so there is no guarantee that all certificate issuances will be reported.
The lack of any CAA records authorizes normal unrestricted issuance, and the presence of a single blank issue tag disallows all issuance.[6][8][12] Third parties monitoring certificate authority behavior might check newly issued certificates against the domain's CAA records, but must be aware that a domain's CAA records may have changed between the time the certificate was issued and the time the third-party checks them. Clients should not use CAA as part of their certificate validation process.[6] ExtensionsA draft of the first extension to the CAA standard was published on October 26, 2016, proposing a new account-uri token to the end of the issue property, which ties a domain to a specific Automated Certificate Management Environment account.[13] This was amended on August 30, 2017, to also include a new validation-methods token, which ties a domain to a specific validation method,[14] and then further amended on June 21, 2018 to remove the hyphen in account-uri and validation-methods making them instead accounturi and validationmethods.[15] ExamplesTo indicate that only the certificate authority identified by ca.example.net is authorized to issue certificates for example.com and all subdomains, one may use this CAA record:[6] To disallow any certificate issuance, one may allow issuance only to an empty issuer list: To indicate that certificate authorities should report invalid certificate requests to an email address and a Real-time Inter-network Defense endpoint: example.com. IN CAA 0 iodef "mailto:security@example.com"example.com. IN CAA 0 iodef "http://iodef.example.com/" To use a future extension of the protocol, for example, one which defines a new future property, which needs to be understood by the certificate authority before they can safely proceed, one may set the issuer critical flag: example.com. IN CAA 0 issue "ca.example.net" example.com. IN CAA 128 future "value" See also{{Portal|Computer security}}
References1. ^{{Cite web|url=https://www.feistyduck.com/ssl-tls-and-pki-history/|title=SSL/TLS and PKI History|last=Ristić|first=Ivan|website=Feisty Duck|language=en|access-date=June 8, 2018}} 2. ^{{Cite news|url=https://arstechnica.com/information-technology/2011/08/earlier-this-year-an-iranian/|title=Another fraudulent certificate raises the same old questions about certificate authorities|last=Bright|first=Peter|date=August 30, 2011|work=Ars Technica|access-date=February 10, 2018|language=en-us}} 3. ^{{Cite arXiv|last=Ruohonen|first=Jukka|eprint=1804.07604|title=An Empirical Survey on the Early Adoption of DNS Certification Authority Authorization|class=cs.CR|date=April 20, 2018}} 4. ^{{Cite IETF|title=DNS Certification Authority Authorization (CAA) Resource Record|draft=draft-hallambaker-donotissue-00|last1=Hallam-Baker|first1=Phillip|authorlink1=Phillip Hallam-Baker|last2=Stradling|first2=Rob|date=October 18, 2010|publisher=IETF}} 5. ^{{Cite IETF|title=DNS Certification Authority Authorization (CAA) Resource Record|draft=draft-ietf-pkix-caa-00|last1=Hallam-Baker|first1=Phillip|authorlink1=Phillip Hallam-Baker|last2=Stradling|first2=Rob|last3=Ben|first3=Laurie|authorlink3=Ben Laurie|date=June 2, 2011|publisher=IETF}} 6. ^1 2 3 4 5 6 {{Cite IETF|title=DNS Certification Authority Authorization (CAA) Resource Record|rfc=6844|last1=Hallam-Baker|first1=Phillip|authorlink1=Phillip Hallam-Baker|last2=Stradling|first2=Rob|date=January 2013|publisher=IETF|doi=10.17487/RFC6844|issn=2070-1721}} 7. ^{{Cite web|url=https://cabforum.org/pipermail/public/2017-March/009988.html|title=Results on Ballot 187 - Make CAA Checking Mandatory|last=Hall|first=Kirk|date=March 8, 2017|publisher=CA/Browser Forum|access-date=January 7, 2018}} 8. ^1 {{Cite web|url=https://www.globalsign.com/en/blog/what-is-certificate-authority-authorization-checking/|title=What is CAA (Certificate Authority Authorization)?|last=Beattie|first=Doug|date=August 22, 2017|website=GlobalSign|language=en|access-date=February 2, 2018}} 9. ^{{Cite news|url=https://www.bleepingcomputer.com/news/security/comodo-caught-breaking-new-caa-standard-one-day-after-it-went-into-effect/|title=Comodo Caught Breaking New CAA Standard One Day After It Went Into Effect|last=Cimpanu|first=Catalin|date=September 11, 2017|work=Bleeping Computer|access-date=January 8, 2018|language=en}} 10. ^1 2 3 {{Cite journal|last=Scheitle|first=Quirin|last2=Chung|first2=Taejoong|last3=Hiller|first3=Jens|last4=Gasser|first4=Oliver|last5=Naab|first5=Johannes|last6=van Rijswijk-Deij|first6=Roland|last7=Hohlfeld|first7=Oliver|last8=Holz|first8=Ralph|last9=Choffnes|first9=Dave|last10=Alan|first10=Mislove|last11=Carle|first11=Georg|display-authors=2|date=April 2018|title=A First Look at Certification Authority Authorization (CAA)|url=https://ccronline.sigcomm.org/wp-content/uploads/2018/05/sigcomm-ccr-final163.pdf|journal=ACM SIGCOMM Computer Communication Review|volume=48|issue=2|pages=10–23|doi=10.1145/3213232.3213235|issn=0146-4833}} 11. ^{{Cite web|url=https://www.ssllabs.com/ssl-pulse/|title=SSL Pulse|date=June 3, 2018|website=SSL Labs|publisher=Qualys|access-date=June 9, 2018}} 12. ^{{Cite web|url=https://www.websecurity.symantec.com/security-topics/what-is-certificate-authority-authorization|title=What is Certificate Authority Authorization (CAA)?|website=Symantec|access-date=January 8, 2018}} 13. ^{{Cite IETF|title=CAA Record Extensions for Account URI and ACME Method Binding|draft=draft-ietf-acme-caa-00|last1=Landau|first1=Hugo|date=October 26, 2016|publisher=IETF}} 14. ^{{Cite IETF|title=CAA Record Extensions for Account URI and ACME Method Binding|draft=draft-ietf-acme-caa-04|last1=Landau|first1=Hugo|date=August 30, 2017|publisher=IETF}} 15. ^{{Cite IETF|title=CAA Record Extensions for Account URI and ACME Method Binding|draft=draft-ietf-acme-caa-05|last1=Landau|first1=Hugo|date=June 21, 2018|publisher=IETF}} External links
2 : Transport Layer Security|Domain name system |
随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识,基本涵盖了大多数领域的百科知识,是一部内容自由、开放的电子版国际百科全书。