Timeline for User-friendly TLS certificate validation
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 9, 2015 at 5:46 | history | tweeted | twitter.com/#!/StackSecurity/status/608148057276981248 | ||
| Apr 28, 2015 at 9:59 | comment | added | WhiteWinterWolf | For SSH keys, where there is usually no CA, ASCII Art has been added to simplify human check of a key. However I do not know any similar system applied to X.509 certificates... | |
| Apr 28, 2015 at 8:44 | answer | added | StackzOfZtuff | timeline score: 2 | |
| Apr 28, 2015 at 8:39 | comment | added | WhyNotHugo | @SteveDL: Regrettably, this is not possible in my scenario, that's why I'm attempting to represent the fingerprint in a more readable way. | |
| Apr 28, 2015 at 8:38 | comment | added | WhyNotHugo | Like I said, there is no CA in this scenario. It's no possible to rely on one either since users can generate their own certificates ad-hoc (and possibly, with no Internet connection). | |
| Apr 28, 2015 at 8:37 | history | edited | WhyNotHugo | CC BY-SA 3.0 |
added 251 characters in body
|
| Apr 28, 2015 at 8:33 | comment | added | Steve Dodier-Lazaro | Build networks of trust? E.g. you validate the first few clients, or add trusted clients which you manually validate, and then your app can find clients that trust clients that trust clients that trust their peer, and validate it... There's plenty of literature on this kind of applications, so you could estimate how quickly and how often that would work for your app. | |
| Apr 28, 2015 at 8:28 | comment | added | BadSkillz | Isn't this exactly what the CA is for? | |
| Apr 28, 2015 at 8:28 | comment | added | Lucas Kauffman | That's why we have CAs... | |
| Apr 28, 2015 at 8:18 | review | First posts | |||
| Apr 28, 2015 at 8:21 | |||||
| Apr 28, 2015 at 8:11 | history | asked | WhyNotHugo | CC BY-SA 3.0 |