3 ms·
if i type https://gmail.com/ https://gmail.com/ into my browser, it usually doesn't matter if you have successfully gotten comodo or actalis to issue you a fake
by kragen 4y ago
if i type https://gmail.com/ https://gmail.com/ into my browser, it usually doesn't matter if you have successfully gotten comodo or actalis to issue you a fake certificate for gmail.com, because my browser doesn't try to connect to your malicious server; it tries to connect to google's actual gmail server, and so you don't receive my packets, and your fake certificate does you no good
but, as i said, if you can feed me fake dns results so i connect to the wrong ip, or if you can arrange so that packets to gmail's legitimate ip go to your server instead (for example by having me connect to your wifi), then you can leverage the fake certificate into a successful mitm attack
but your explanation of the part of the basics of tls you understand, incomplete though it is, is irrelevant to the attack i was actually discussing, where someone doesn't like what you're saying (or the communication service you're providing) and gets your cert revoked to shut you up
- b112 4y agobecause my browser doesn't try to connect to your malicious server Unless a router is compromised along the route, which is a known thing, and part of why we use ssl everywhere now.
- kragen 4y agothe paragraph immediately following the one you quoted from explains that, and did so nine hours before your comment the grandparent comment https://news.ycombinator.com/item?id=34629050 https://news.ycombinator.com/item?id=34629050 also describes some more common ways that this can happen without routers being compromised
- b112 4y agoNoted.