I posted in the Mozilla Help Forum with more details than I did here but
still didn't find a solution. I finally tried overwriting cert8.db and
secmod.db from one of the other two computers that were still OK. And
that cured it. Of course it will happen again as it has to all three
computers so
This sounds like something a bug needs to be filed on.
If you have openssl, can you do:
openssl s_client -connect 192.168.168.132 -showcerts
and send the dump thereof?
My instant thought is that there might be an IP address in a
subjectAltName entry of type dNSName, or an IP in the Common Name
I am pasting a post I made on June 7th in the mozilla.support.firefox
group. Someone in that group suggested I bring the problem here. I'll add
a bit at the end...
--
Our telephone company controls equipment by accessing the card
This should be on crypto, not security, transferring. I have an hard
time testing it fully because of time-outs on vps-serv-1.ausnetservers.net
But the problem seems to be :
- With Firefox 4, adding an exception for a cert on domain X prevents
from continuing to accept this cert as valid on dom
This from one of the posters to our Mozilla Contribute List/Forum:
Hi,
i was 110% sure that there was an issue with the new Fixfox 4 and i was
right!
The issue only occurs when you add a ssl certificate that is
