Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
If its time based (as it should be) it won't be sent anywhere. It's generated on the phone and verified by the website. Both are more or less just RNGs, seeded with the same value.
-
@dIREsTRAITS
The problem with SMS is... That it's like sending a pigeon carrying a letter.
SMS has zero security. Like none. Nothing. Nada. Niente. Nullo.
You're sending a clear text password over an unencrypted, interceptable communication owned by multiple foreign parties (service providers, government, ...). -
tedge3013yOk after the shit I’ve seen I could totally see someone doing this. It would be some php developer who implemented otp via sms. An attacker could then log in as any user by requesting a otp for that user.
It would be better to send otp by email.
sms is ok for 2fa, only because it’s better than 1fa -
@tedge wait what, of course 2nd factor. I hope OP isn't talking of the 1st factor here? That would be complete bogus.
Guys, is it possible to catch OTP code sent from a website to phone through the browser just because of a lack of security practice and weak coded script?
question