4 ms·
The article says: > Because Secure Time Seeding used SSL certificates Windows already stored locally, it could ensure that the machine was securely connected t
by cpeterso 3y ago
The article says:
> Because Secure Time Seeding used SSL certificates Windows already stored locally, it could ensure that the machine was securely connected to the remote server. The mechanism, Microsoft engineers wrote, “helped us to break the cyclical dependency between client system time and security keys, including SSL certificates.”
But in that case, why does the Windows time service connect to a random server running OpenSSL instead of a trusted server under Microsoft's control like time.microsoft.com (or whatever)?
- pixl97 3y ago>instead of a trusted server under Microsoft's control like time.microsoft.com (or whatever)? "Golly it's getting expensive hosting 100 billion random requests per year, lets let someone else shoulder the problem". While this might not be it, we've seen plenty of other providers really screw up with time like this. I believe it was Linksys years ago just pointed their NTP as someone elses NTP servers and flooded them out.
- X-Cubed 3y agoNot all PCs are on the internet or have access to time.microsoft.com