>> I was looking for more information. Why can't we secure it? > Daniel explained it to me once, but I've forgotten the details. Perhaps he'll > speak up.
The delay/replay problem is fatal, at least with a simple public key system like I proposed. There is probably something like a FAQ entry that explains that if you want to get time relevant data from A to B, you have to start by sending something from B to A, a nonce if nothing else. You could eliminate duplicates by having the sender include a sequence number. You would have to add a dance to get started. I don't see how to protect against delays without sending something from B to A -- or knowing the time. >> I'm not sad to see broadcast modes gone. It was tangled up with a >> state machine which I never really understood. > And may no longer exist since Daniel's massive refactor of the protcol > engine! I removed the state machine after we had removed enough stuff (like broadcast and peers) so that the remaining cases were simple enough to understand. That was a while ago. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
