Timeline for Using a verified certificate to sign others
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 6:58 | history | edited | CommunityBot |
replaced http://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Sep 22, 2012 at 13:09 | comment | added | Paystey | Yes it's only for personal use, but from multiple browsers so I can't really install, but I'd still be able to view the chain as intact right? The browser just wouldn't be happy with it? | |
| Sep 21, 2012 at 23:47 | comment | added | ewanm89 | @Paystey if it's only for your own use, why not create your own root CA and just sign with that? And install it as root cert in browser? | |
| Sep 21, 2012 at 21:29 | comment | added | Paystey | OK For bonus points. If I did this anyway and signed my own certs with it, it still wouldn't be susceptible to man in the middles right? because I'd still be able to see the full chain, and see my cert -> verified by my own cert -> verified by the CA? It's just the browser that would complain. | |
| Sep 21, 2012 at 21:27 | vote | accept | Paystey | ||
| Sep 21, 2012 at 21:21 | history | answered | Thomas Pornin | CC BY-SA 3.0 |