大网数据广告活动
服务器运维问答

Less restrictive CAA record for subdomain

· 52CE 我爱测

I have a root domain I have control of and a set of subdomains, but other people are responsible for them. I want to add a CAA protection to my root domain, but I don't want to restrict the subdomain users from using certificatio…

问题原文

原帖链接 · basin · CC BY-SA 4.0

I have a root domain I have control of and a set of subdomains, but other people are responsible for them.

I want to add a CAA protection to my root domain, but I don't want to restrict the subdomain users from using certification authorities of their choice.

Unfortunately, subdomains inherit the issue tag of a parent domain. Is there a technical possibility to allow any authority issue a certificate to a specific subdomain? An empty string means "no one".

已采纳解答

原帖链接 · Håkan Lindqvist · CC BY-SA 4.0

Based on just looking at the CAA spec, it appears that it should be technically possible to do what you are requesting.
However, it's not a scenario that I have seen discussed elsewhere and it seems plausible that it may not have been considered by CA's when implementing their CAA validation.

The approach that looks possible in the spec boils down to this:

  • RFC6844 section 4 (Certification Authority Processing) describes how the CA should locate the relevant CAA record set by starting at the name specified in the certificate request and using the first non-empty CAA RRSet that they encounter as they work themselves towards the root.
  • RFC6844 section 5.2 (CAA issue Property) describes how it is the use of the issue property tag which request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers. (And section 5.3 describes how issuewild works with overall the same semantics but being specific to requests with wildcard names.)

This leads me to the conclusion that, if you were to publish CAA recordsets which contain no records with issue or issuewild as their tag in these subdomains, according to the spec it seems that these subdomains should be unrestricted. An example of such a CAA RRset would be only a record with the iodef tag.


YMMV, it may turn out to be more practical to either just publish actual `CAA` issuance policies for the subdomains or alternatively forego `CAA` entirely.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2019-01-01)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。