Timeline for Can SSL requests be proxied by issuing a second certificate?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 26, 2013 at 15:37 | comment | added | makerofthings7 | I think the OP is asking something different. His question reads to me like this: "If the malicious bank has a legitimate SSL certificate (through normal acquisition measures) and the the HTTP listener on evilBank's port 443 is a proxy that creates a session with thebank.com. This would make a MITM possible, and is orthogonal to the attack you describe | |
| Jan 25, 2013 at 22:29 | comment | added | user20033 | @owlstead beat me to it by 1 minute!! | |
| Jan 25, 2013 at 22:28 | comment | added | user20033 |
But how does the browser know it expects to see www.thebank.com? If the user clicked on a malicious link then the browser address bar will contain the malicious URL and the browser has no way of knowing this is not a legitimate action, right? Of course, all savvy people will check the address bar to see what site they are connecting to, but I am thinking of the majority of people who don't do that and are caught out in these kinds of attacks, and if there is any way to prevent it.
|
|
| Jan 25, 2013 at 22:26 | comment | added | Maarten Bodewes | Most of the time it is probably Alice that doesn't notice that the website is on a server with a different URL. In that case there are no issues with certificates, and the attack works. There will always be CA's willing to sell a certificate for a site whose name is close to that of another site. | |
| Jan 25, 2013 at 16:18 | history | answered | Thomas Pornin | CC BY-SA 3.0 |