Closed Bug 702947 Opened 14 years ago Closed 13 years ago

untrusted connection for www.midnight-commander.org

Categories

(Firefox :: Security, defect)

8 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: applezinc, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0 Build ID: 20111104165243 Steps to reproduce: Using Linux 32bit Version 8.0 Firefox 1) goto https://www.midnight-commander.org/ Actual results: This Connection is Untrusted You have asked Firefox to connect securely to www.midnight-commander.org, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. Technical Details www.midnight-commander.org uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for midnight-commander.org (Error code: sec_error_untrusted_issuer) Expected results: The web page should have opened. There is nothing wrong with the site. Opera web browser has no issue with the site.
Mozilla/5.0 (X11; Linux x86_64; rv:11.0a1) Gecko/20111116 Firefox/11.0a1 Opera and Chrome display the site as insecure for me, just like Firefox.
WFM if I add a security exception, and they all display that the site is insecure: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 Mozilla/5.0 (X11; Linux x86_64; rv:11.0a1) Gecko/20111116 Firefox/11.0a1 Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.10.229 Version/11.60 Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
please reopen, that's more than annoying.
You need to log in before you can comment on or make changes to this bug.