3 ms·
I think the OP is dead on. The goal here is to encrypt your connection, not to bypass industry-standard security measures. Once you install the cert (client-s
by zupreme 15y ago
I think the OP is dead on. The goal here is to encrypt your connection, not to bypass industry-standard security measures.
Once you install the cert (client-side) you are protected just as you would be with a publicly signed cert. If you are ever subjected to a Man-In-The-Middle attack or a spoofing attempt, the exact same flags would occur.
This is not a solution for eCommerce, or for your web-app's user sign-in page. This is for your admin panel and backend which only you (or your staff if you have one) will be using.
If you actually install the cert to your local certificate store (as opposed to just cancelling out of the alert) you should be solid.
Great post Josh.
- AjithAntony 15y agoAnother detail he kinda neglected, is that if you don't want browser warnings, the then common name of the subject(or an alt name) needs to match the host the user connects to. Having a cert for "www.joshbetz.com" in your cert store does not preclude the warnings about the host name mismatch when you visit joshbetz.com/
- joshbetz 15y agoThanks for pointing that out. Safari wasn't giving me any warnings, but Chrome definitely does.