Timeline for How can a domain be impersonated with a fraudulent SSL certificate?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 12, 2015 at 12:24 | vote | accept | Ryakna | ||
| Mar 9, 2015 at 16:15 | comment | added | M'vy | Quite true @Stephane, edited accordingly. | |
| Mar 9, 2015 at 16:15 | history | edited | M'vy | CC BY-SA 3.0 |
added 121 characters in body
|
| Mar 9, 2015 at 16:13 | comment | added | Stephane | You're forgetting about direct MITM attacks: if I control a router in the path between you and the target system, I am free to redirect all traffic to my own system and perform a MITM that way without messing with DNS. I could use any and all compromized certs (root or otherwise) in such a case. "free wifi", anyone ? | |
| Mar 9, 2015 at 15:27 | comment | added | Iszi | Compromised Root CAs are also useful to any MitM between the client and its Internet gateway. That's essentially how corporate SSL proxies work, though in those cases the Root CA isn't technically "compromised". | |
| Mar 9, 2015 at 15:18 | history | answered | M'vy | CC BY-SA 3.0 |