4 ms·
This already kind of happens in Firefox. If you have a non public certificate authority, when you visit a site signed by that CA it says that it's not verified
by vladvasiliu 6y ago
This already kind of happens in Firefox. If you have a non public certificate authority, when you visit a site signed by that CA it says that it's not verified by an authority known to Firefox.
I don't know if there is a way to "bless" such an authority once it's added to the trust store.
- toyg 6y ago? If it’s added to the trust store, it should be blessed. Note that this is the FF store, not the Windows one.
- extra88 6y agoWhat browser doesn’t warn you about sites signed by a CA not in their list of CAs?
- vladvasiliu 6y agoI specifically said "once it's added to the trust store". It is known to the browser. When I wrote the message I wasn't in front of Firefox, now I am. So to summarize: * The CA's certificate is added to the Firefox store and trusted. * Visiting a site gets the lock in the address bar. * Clicking on the lock in bar shows "Connection secure. Connection is verified by a certificate issuer that is not recognized by Mozilla" Screenshot: https://imgur.com/a/T4rznXK https://imgur.com/a/T4rznXK
- extra88 6y agoSo what’s the problem? Mozilla didn’t add the CA to the trust store, you did, that’s why Mozilla doesn’t recognize it. It doesn’t sound like it interferes with normal operation and differentiating bundled and added CAs on inspection sounds like a good idea.
- gspr 6y agoThis is a completely different matter.