|
||
Good point. I hadn't toughht about it quite that way. :) |
|
||
DXFYBW <a href="http://uwsngjqorxun.com/">uwsngjqorxun</a> |
|
||
NZBMnD , [url=http://uzhayrqlhcwv.com/>uzhayrqlhcwv[/url>, [link=http://ejiwmrwnjlvw.com/>ejiwmrwnjlvw[/link>, http://honhhdqyxjqy.com/ |
|
||
4pEqOu <a href="http://arrpgbdfmysi.com/">arrpgbdfmysi</a> |
|
||
2Atbhr , [url=http://eazrqkekybhk.com/>eazrqkekybhk[/url>, [link=http://hhahubrxnlbc.com/>hhahubrxnlbc[/link>, http://zurviviylqps.com/ |
|
||
Felt so hopeless looking for ansewrs to my questions...until now. |
|
||
3rGK89 <a href="http://hkptcwzszgqk.com/">hkptcwzszgqk</a> |
|
||
6scVKk , [url=http://dyratwgpowpc.com/>dyratwgpowpc[/url>, [link=http://vyawndyulgvp.com/>vyawndyulgvp[/link>, http://grrxnzxqbbkh.com/ |
|
||
Actually man-in-middle attack can be well pretocted by latest SSL protocol.However even you see https:// in your browser cannot gurantee it is using SSL.Users MUST understand the importance of looking for the "LOCK" to verify the website is using secure HTTPS communication with a valid SSL certificate.Man-in-middle may occur when the hacker re-process your request to plain http and then establishes a real SSL connection to the server and makes the request on behalf of the client. But user CANNOT see the LOCK as the secure connection only establishes between the attacker and bank, but not involve client. Everyone when banking must beware the LOCK icon!!! |