User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050512 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050512 Firefox/1.0+ When i try to open the website https://www.ultimatix.net, i am unable to see the web page. I gives me an error that invaild certificate. but the IE opens the website without any errors. Reproducible: Always Steps to Reproduce: 1.open the website https://www.ultimatix.net 2. 3. Actual Results: i am getting a dailog box stating that Could not establish an encrypted connection because certificate presented by www.ultimatix.net is invalid or corrupted. Error Code: -8102 Expected Results: show the contents of the website
*** Bug 294471 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 143280 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → DUPLICATE
Can you please explaint wrt this website https://www.ultimatix.net? And I am a layman in understanding the SSL intricasies
The website is serving a security certificate marked as invalid for use as an SSL server certificate. Therefore Firefox will not accept it, Internet Explore ignores this fact and accepts the certificate anyway. Therefore the website needs to reconfigure their server to send a valid certificate.
Can you have a lok at the website's certificate? I want you to have a detailed look into the website's certificate? Because this is my corporate's employee website. we have access this site entering timesheets, viewing you monthly pay slips, etc. i want to access the site through the mozilla also.
The server cert being used says it is valid only for these uses: Name: Certificate Key Usage Usages: Digital Signature Non-Repudiation Since the cert bears an RSA public key, SSL requires it to be valid for KeyEncipherment.
Can you please tell how to check the certificate validity?(any utility) I saved the certificate in X.509 type file with base64 encoding and pkcs format. (2 files)
You need to log in before you can comment on or make changes to this bug.