|
|
|
|
|
by samgranieri
482 days ago
|
|
Hmm. I wonder how this will work with certificates generated by enterprise or private certificate authorities. Specifically, I use caddy for local web development and it generates a snake oil ca for anything on *.localhost using code from step-ca. I also use step-ca and bind to run a homelab top level domain and generate certs using rfc2136. I have to install that root ca cert everywhere, but it’s worth it |
|
I haven't tested Firefox's implementation yet, but I expect your private CA to continue working as expected since it is manually added.
Private CAs can:
* Issue longer certificates, even 500 years if you want. Public CAs are limited to 1 year I think, or 2? I think it was 1..
* Can use weaker algorithms or older standards if they want.
* Not subject to browser revocation policies - no need for OCSP/CRL etc.
* More things that I do not know?