Timeline for What is the risk of someone else having access to your SSL certificate?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 5, 2016 at 21:10 | vote | accept | vic | ||
| Sep 5, 2016 at 11:14 | comment | added | Steffen Ullrich | @Philipp: DNSSec does not help if the attacker already controls the path of the connection, i.e. with ARP spoofing, owning the router, owning the access point etc. DNSSec only helps against DNS spoofing which is only one of many ways for an attacker to control the flow of the connection. | |
| Sep 5, 2016 at 10:59 | comment | added | Philipp | This is why DNSSEC is important. It adds digital signatures to DNS records. Unfortunately it isn't widely adopted yet. | |
| Sep 5, 2016 at 10:54 | history | edited | SilverlightFox | CC BY-SA 3.0 |
added 1 character in body
|
| Sep 5, 2016 at 10:25 | comment | added | vic | That was the missing piece, thanks for jump starting my brain. Basically, the attacker must be able to manipulate the DNS in some way in order to (mis)use the rogue certificate. The way I see it, there are only three ways, please correct me if I'm wrong or if there are more. 1) The attacker controls the network. 2) The attacker has write access to the users's hosts file. 3) The attacker has access to the authoritative DNS Server. | |
| Sep 5, 2016 at 10:15 | history | edited | Maarten Bodewes | CC BY-SA 3.0 |
added 14 characters in body
|
| Sep 5, 2016 at 10:09 | history | answered | Maarten Bodewes | CC BY-SA 3.0 |