This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/

[dns-wg] What about the last mile, was: getting DNSSEC deployed

• Previous message (by thread): [dns-wg] What about the last mile, was: getting DNSSEC deployed
• Next message (by thread): [dns-wg] What about the last mile, was: getting DNSSEC deployed

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Lutz Donnerhacke lutz at iks-jena.de
Mon Feb 19 10:28:19 CET 2007

* Max Tulyev wrote:
> Lutz Donnerhacke wrote:
>> If you use a validating resolver on your end side, DNSSEC detects and
>> prevents this attack.
>
> How? As I understood, the idea of the attack is to change DNS, not to
> poison it.

If you always get the right answer, this attack does not harm.

• Previous message (by thread): [dns-wg] What about the last mile, was: getting DNSSEC deployed
• Next message (by thread): [dns-wg] What about the last mile, was: getting DNSSEC deployed

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]