@cksChris Siebenmann did you ever have any luck with TLS root certificate authority using name based constraints?

I have read two of your wandering thoughts posts about it and I’m curious if you have any time derived insight.

I have a constrained root (permitted;DNS.1 example.net permitted;IP.1: 192.0.2.0/255.255.255.0) and struggling with what to do about unqualified / short names.

In an unconstrained root, it’s trivial to add the unqualified name to the subjectAltName of the leaf certificate.

But the combination of name based constraints and unqualified names is still bothering me.

Arguable the name based constraint is doing exactly what it should.

I’m hoping to avoid listing a bunch of unqualified host names as additional DNS.# entries in the root CA’s config.

I’m curious what your experience was / is and if you have any recommendations.

0

If you have a fediverse account, you can quote this note from your own instance. Search https://oldbytes.space/users/drscriptt/statuses/115359168931937957 on your instance and quote it. (Note that quoting is not supported in Mastodon.)