Closed Bug 667857 Opened 15 years ago Closed 15 years ago

ssl_error_no_cypher_overlap

Categories

(Firefox :: Security, defect)

5 Branch
All
Other
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: suburp212, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0 Build ID: 20110615151330 Steps to reproduce: try to access https://xms.lvs.dupont.com/ Actual results: connection failed Error while connecting to xms.lvs.dupont.com. Unable to secure communication with peer: no generic encryption algorithm (s). (Error code: ssl_error_no_cypher_overlap) The page you want to view can not be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them about this problem. You can also use the command in the help menu to report this broken site. Expected results: page should have opened, it works in Iexplorer
I can't reach that site, is it inside a corporate intranet? Assuming you did not disable any standard ciphers in your browser (which cannot be done by accident) you really need to do what the message says and report this to the administrators of that site. They appear to have chosen a narrow set of ciphers that do not include any of the standard ones supported by Firefox. Without being able to reach the site I cannot begin to guess if this is simply misconfiguration or if there's some property of the cipher they picked that is required by their business and they're OK having an explorer-only site. If this is a relatively new cipher that IE implements and that should be added to Firefox then a "feature request" bug would be reasonable, but there is not enough information here to know what the feature is.
Group: core-security
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
I concur with everything Dan has said in comment 1. Please reopen if you can provide information which would enable us to reproduce this bug.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.