Timeline for What is the risk of someone else having access to your SSL certificate?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2019 at 11:25 | answer | added | AB123 | timeline score: 0 | |
| Sep 5, 2016 at 21:10 | vote | accept | vic | ||
| Sep 5, 2016 at 11:59 | comment | added | vic | @SteffenUllrich My question is what one can do with a certificate for a domain he does not own. I just mentioned g00gle.com as an example that would, in my understanding, not work. That's why I was asking for examples how such a certificate could be misused. The answer you gave in the linked question is helpful. | |
| Sep 5, 2016 at 11:09 | comment | added | Steffen Ullrich | @vic: CA is certificate agency which is not short for certificate but some entity which issues certificates. While you've fixed this "typo" it is still unclear if you ask what somebody can do with a valid certificate for a domain he does not own (google.com) or with a certificate for a similar sounding domain he does own (g00gle.com). If you are interested in both then please ask two question because these are different issues, i.e. man in the middle attack vs. phishing. | |
| Sep 5, 2016 at 10:34 | history | edited | vic | CC BY-SA 3.0 |
changed CA to certificate
|
| Sep 5, 2016 at 10:33 | review | Close votes | |||
| Sep 5, 2016 at 14:05 | |||||
| Sep 5, 2016 at 10:14 | comment | added | vic | I wish to understand which types of attacks are possible or likely using a rogue certificate. | |
| Sep 5, 2016 at 10:09 | answer | added | Maarten Bodewes | timeline score: 3 | |
| Sep 5, 2016 at 10:07 | comment | added | Yorick de Wid | Your title does suggest something else than the post. Are you talking about risk, or do you want to know how this attack could be made possible? Also have a look at security.stackexchange.com/q/135714/59575 | |
| Sep 5, 2016 at 9:41 | history | asked | vic | CC BY-SA 3.0 |