Skip to content

Commit 71d45b1

Browse files
committed
mention TCB and DNSsec
1 parent c3b7706 commit 71d45b1

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

infra.rst

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -860,6 +860,16 @@ operation of the Internet. While DNSSEC has struggled to gain
860860
traction, other methods of protecting DNS have appeared more
861861
recently and are having some impact, as discussed in the next section.
862862

863+
The challenges of securing DNS illustrate a point we made early in
864+
the book about the trusted computing base (TCB) and minimizing its size. If
865+
DNS needs to be trusted in order for systems that depend on the
866+
Internet to operate securely, then we have chosen a large, distributed system
867+
component that needs to be made secure. Having largely failed to make
868+
DNS secure over thirty years, it is a good thing that TLS (and other
869+
systems using end-to-end encryption) provides secure communications
870+
over untrusted infrastructure. In other words we have excluded DNS
871+
from the TCB.
872+
863873
A final note on DNSSEC is that, by making responses larger, it has the
864874
potential to worsen amplification attacks. The response to a request
865875
to a DNS server that implements DNSSEC contains both a signature and

0 commit comments

Comments
 (0)