Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

slight rewrite of explanation of _ underscore protection #64

Merged
merged 3 commits into from
Aug 21, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions draft-ietf-dance-architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -418,9 +418,13 @@ Compartmentalizing failure domains within an application is a well-known archite
Within the context of protecting DNS-based identities, this compartmentalization may manifest by hosting an identity zone on a DNS server which only supports the resource record types essential for representing device identities.
This can prevent a compromised identity zone DNS server from presenting records essential for impersonating web sites under the organization’s domain name.

The naming pattern suggested in <https://datatracker.ietf.org/doc/html/draft-huque-dane-client-cert> includes
an underscore label (_device) which also prevents the issuance of Web PKI-validating certificates in the
event a DNS server hosting a client identity zone, which is capable of presenting A and AAAA records, is compromised.
The naming pattern suggested in {{I-D.ietf-dance-client-auth}} includes
an underscore label (_device).
The underscore is not a valid character for names used in the Web PKI.
This prevents the issuance of any Web PKI-validating certificates for these names.

This means that even were the authoritative DNS server compromised, it would not be possible to issue Web PKI certificates using, for instance, the {{?RFC8555}} DNS-01 challenge.

An alternative underscore label _user separates the TLSA records with the domain CA from the TLSA records for devices.

## Availability
Expand Down
Loading