3 ms·
You're overestimating. See RFC6238 for time based one time passcodes. It is a fairly simple truncated SHA hash of a shared secret (random fixed length string)
by jqpabc123 4y ago
You're overestimating.
See RFC6238 for time based one time passcodes. It is a fairly simple truncated SHA hash of a shared secret (random fixed length string) with a UTC timestamp. Build your own or look for code on the internet.
Once you can generate and verify a proper hash (https://totp.danhersam.com/ https://totp.danhersam.com/), it is simply a matter of getting the user to do likewise. This can be done using an app (I like FreeOTP+) or you
can generate the hash value yourself and delivery it to the user over SMS or email or voice call or carrier pigeon or any other off channel way you can think of.
Obviously, there are details to be worked out but the overall process is "kindergarten algebra". In your case, the biggest hiccup is likely to be USSD.