I was under the impression that this system mostly used Microsoft services, but if they take all TLS handshakes as input then that does make more sense. The fix also seems rather obvious (only use Microsoft connections with certificate pinning for time source input, since Windows will talk to Microsoft every minute anyway).
Even if openssl/boringssl was spec compliant as Microsoft assumed (hasn’t been for almost a decade of course) you’d still want to make sure the data is all close enough just in case you hit a few misconfigured servers. Otherwise you’d get a viral effect where badly configured servers start infecting each other as they communicate.
I was under the impression that this system mostly used Microsoft services, but if they take all TLS handshakes as input then that does make more sense. The fix also seems rather obvious (only use Microsoft connections with certificate pinning for time source input, since Windows will talk to Microsoft every minute anyway).
Even if openssl/boringssl was spec compliant as Microsoft assumed (hasn’t been for almost a decade of course) you’d still want to make sure the data is all close enough just in case you hit a few misconfigured servers. Otherwise you’d get a viral effect where badly configured servers start infecting each other as they communicate.