Kurt Roeckx via devel writes: > There currently isn't a protocol defined between the NTP server > and the NTS-KE. This would mean that if you want to use it with > the pool that such a protocol would need to be defined.
A more practical solution until that's been hashed out is to require an NTS matched to the NTS-KE. > I also don't think NTS is designed for this use case. Maybe Daniel can shed some light on that question, but the fact that a detached NTS-KE is even considered makes it more likely that this use-case at least lingered in some heads. > I'm not sure what the security implications are, but at least hacking > the pool then seems like a way to be able to impersonate all servers > in the pool. The easiest way of dealing with the "protocol" is having a TLS connection between the NTS-KE and each NTS. Its session can be suspended most of the time and resumed rather than re-opened. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
