e...@thyrsus.com said: > I think we'd best completely avoid writing an NTS-KE server until we have > tested our client side against one of the two existing server > implementations.
Then we have to learn how to drive the existing implementations, and learn enough about how they operate so we can insert printfs for debugging. I think I'd be happier working with code and people I'm familiar with. We can bring our client and server up in steps. Dummy KE client and server - just do handshake cookies - pack and unpack via tests KE server returns cookies KE client returns cookies to NTP client NTP client sends cookies to NTP server. NTP server decodes/processes cookies. NTP server sends back new cookies. We can get a layer of parallelism by using dummy cookies. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
