roughtime
roughtime copied to clipboard
A secure clock-synchronization protocol for when rough is enough.
Hi all, A common problem faced by many is that DNS-over-HTTPS won't work if your clock is wrong, and you can't fix your clock because you can't resolve NTP domain...
To reproduce: Start a couple of Roughtime servers: ``` $ go run ./cmd/testserver -addr 127.0.0.1:2002 main.go:64: Root public key: sm2tho24GOkdU26vpQInrruJKumCEDLCVHTArPBPqDY= ``` ``` go run ./cmd/testserver -addr 127.0.0.1:2003 main.go:64: Root public...
At the moment this function returns the serialized request and, separately, the nonce used to verify the response. One way to clean up this API is to return a `*Request`...
As of draft 11, the server SHOULD grease its response as described in Section 8. We currently don't implement this at all.
It looks `delay` is a rolling sum of all the server requests' round trip times. I may be mistaken, but it doesn't make sense for the new median calculation, delay...