Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
I suspect both, but hey.
Google is your friend.
I don’t want that to ruin my search history so could you explain in person? XD
"Problem Exists Between Keyboard And Chair".
Which is just a glorified way of saying the average user is not very smart.
It's an oldie and probably more likely to be familiar to someone with some IT background, or just old enough to have heard a thousand and four acronyms.
They'd have to communicate somehow, otherwise you could just plug in any random value when Steam asks for a Guard Code. The "current time" factor for example would demand that both devices be synced with the same NTP Server. It's pretty trivial for Steam to be able to query any NTP Server anywhere, but if the phone had been offline for as little as 20-30 minutes there's going to be "drift." All drift means is that a computer can only account for time by the number of processor cycles or ticks that occur, and at the speed modern CPUs run there's always going to be some float value remainder when you divide the number of ticks that have passed by the number of ticks the CPU generally makes per second. There are other factors, but that's a big one. I can't see how either end could reliably generate a code and have the other recognize it without some kind of synchronization between the two.
Uhm, no.
There is a slight delay between the generation and the timecode used (if you are fast enough to input, your code is actually still invalid). Both use Unix time anyway. So yes, your device shouldn't be off too much, but there is no need to communicate between server and generation device. Standalone 2FAs are completely offline.