I don't understand why the error message from the store was nothing more than an error code, and why the MSKB for that code had absolutely no mention of a failed ssl negotiation as a possible cause.

[–] rumba@lemmy.zip 1 points 1 day ago (1 children)

Time->TLS errors aren't handled well anywhere.

As critical as they are to 2fa and TLS, you'd think every OS out there would poke around a few time servers and scream bloody murder if the time was off.

Honestly, I think we, as a society, have leaned a little too hard into time as a precise critical failure point. It's fine for things like GPS that actually require it. but our clocks don't need to be precisely the same to tell how recent a request and response are and we can certainly make better hashing algos

[–] Windex007@lemmy.world 3 points 1 day ago

wget will give you a sniff of what the problem is. Microsoft Store will not.

I don't NEED an application to necessarily pinpoint the error. Just even a rough direction. Any browser will explicitly tell you if there is a cert issue. That's more than enough to go on.