> I think the point with this oven is not that it needs an accurate > clock to do localroot, it's that it needs an accurate clock > (amongst other things) to do DNSSEC validation. It's the ability > to validate that would be the direct requirement for localroot.
An accurate clock is easy to come by if you have internet access. Just ask pool.ntp.org. The question is whether we need an accurate clock that is also secure. I'd say no, because all an attacker can do is make the local root fail and then the resolver will fall back to the normal root. At most this is a DoS. And for that the attacker has to insert themselves into pool.ntp.org or be able to intercept traffic. Hard work and essentially nothing in return. So spoofing time is in this case not an effective attack. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
