Re: (short version) Re: Last Call: <draft-faltstrom-uri-10.txt> (The Uniform Resource Identifier (URI) DNS Resource Record) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "Eliot" == Eliot Lear <lear@xxxxxxxxx> writes:


    Eliot> DNSSEC: it's not just for breakfast anymore.

I've mentioned this before, but DNSSec is not really a complete answer
here.
DNSSec is only an appropriate answer when the set of DNS trust anchors
are appropriate to the information being protected.

Today, I expect for many applications that the information entered by
the user will be validated against an application-specific set of trust
anchors.  If DNS is trusted to make decisions about what my target
security principal can be, then the DNS trust anchors become part of
that trusted set.  For a number of enterprise applications that's really
bad from a security standpoint.

For other applications, this is a great technology and DNSSec is a
reasonable way to protect it.





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]