Timeline for Why IE/Windows forces you to install self-signed certificates as root CA to make them work?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 21, 2016 at 19:12 | comment | added | Phil Lello | Unfortunately this is a symptom of a trend; increasingly the IETF HTTPWG and browser vendors feel that end users can't be trusted to make their own security decisions. Sadly, anecdotal evidence supports their position. | |
| Aug 8, 2013 at 11:05 | comment | added | LatinSuD | I want to trust certificate "C" for site "S" only. When I install "C" as a root CA i'm potentially allowing "C" to impersonate anything. | |
| Aug 7, 2013 at 13:18 | history | edited | Thomas Pornin |
edited tags
|
|
| Aug 7, 2013 at 13:17 | answer | added | Thomas Pornin | timeline score: 5 | |
| Aug 7, 2013 at 12:56 | comment | added | Ramhound | If you trust the self-signed certificate what security problems are you worried about? The purpose of any certificate is to allow the client to verify the server is the server they are talking to. | |
| Aug 7, 2013 at 12:48 | comment | added | zedman9991 | Trust is central to your question. As Peter Gutmann says "Revoking self-signed certificates is hairy". Check out cs.auckland.ac.nz/~pgut001/pubs/pkitutorial.pdf to get a better understanding of the trust issues. | |
| Aug 7, 2013 at 9:55 | review | First posts | |||
| Aug 7, 2013 at 10:55 | |||||
| Aug 7, 2013 at 9:39 | history | asked | LatinSuD | CC BY-SA 3.0 |