3 ms·
That's why 2FA should be performed at transaction confirmation time for sensitive operations, not just at login or periodically.
by lxgr 7y ago
That's why 2FA should be performed at transaction confirmation time for sensitive operations, not just at login or periodically.
- deleted 7y ago[deleted]
- mlyle 7y agoEven then; substitute the transaction they want for another transaction. If the device you are using is compromised, you're in for a bad time. You could send some simple transaction summary to the other device to acknowledge, which is getting better. Even so that doesn't completely eliminate the opportunity for tomfoolery.
- pastage 7y agoIf you sign with a 2FA I can not see how a compromised computer can make that insecure. Though I will say, the UX on 2FA signing needs to get better, but it is secure enough.
- mlyle 7y agoIf the 2FA doesn't contain the actual transaction detail, pretty simply. When user tries to transfer $1,000 of cash from user's investment account to user's bank account, instead, initiate transferring $100,000 to EvilGuy's bank account. Rewrite elements so it appears that $1,000 is being transferred to user's bank account, and wait for user to receive their 2FA code and authenticate. This may be as easy as string replacement both ways.