Re: [Ntp] Antwort: Re: Antwort: Why Roughtime?

[Hal Murray <[e-mail]>]

Watson Ladd said:
> How would you put it in? Signing the response takes significantly longer than
> you want in NTS.

NTS already signs each packet.  The catch is that the key used for the signing 
is a shared secret setup by NTS-KE.  What's missing is a way to prove that the 
key the client is using was used by the desired server.  We can get that by 
extending NTS-KE to include signing the shared keys.

Using this approach would allow you to monitor every NTP+NTS transaction 
rather than only an occasional Roughtime refresh.


> Having a long term identity runs at cross purposes to relying on the WebPKI.

Right.  We would have to bypass the WebPKI.  We can do that with self signed 
certificates.  It looks like we would be using the WebPKI because the public 
key is embedded in a certificate but it's not using their (relatively) short 
lifetime root certificate collection.  If you can distribute a long lifetime 
key for Roughtime we can do the same to distribute a long lifetime certificate.

I'm not a WebPKI wizard.  I'm using self signed certificates for testing so 
most of the code for that path already works.


-- 
These are my opinions.  I hate spam.