3 ms·
This article is silly and i would argue dangerous. One of the applications they suggested is MFA. If you're validating mfa on the client side you are doing it
by bawolff 6y ago
This article is silly and i would argue dangerous.
One of the applications they suggested is MFA. If you're validating mfa on the client side you are doing it wrong.
They give 3 ways to deal with MITM attack. PKI isn't mentioned as one of them. Who the hell tries to deal with MITM by looking at network timings?
There's a reason that the api has subtle in the name, its because using it naively will shoot yourself in the foot. Unless you have a very specific usecase,leave the crypto to the tls layer.
- deleted 6y ago[deleted]
- game_the0ry 6y ago> One of the applications they suggested is MFA. If you're validating mfa on the client side you are doing it wrong. Agreed. > Unless you have a very specific usecase,leave the crypto to the tls layer. Agreed. Author should delete that blog post. Normally, I wouldn't suggest that, but since this is dealing with security, it should thoroughly scrutinized, especially since there are so many JS noobs just starting their careers and they might look at this post as best practices.