Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

After refreshing Firefox Beta 39.0, the browser will not open a website that opens in a new tab.

  • 10 réponses
  • 306 ont ce problème
  • 1 vue
  • Dernière réponse par derek500

more options

"SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. (Error code: ssl_error_weak_server_ephemeral_dh_key)

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem."

The page used to load in a new tab before I selected to Refresh Firefox. I cannot find out how to allow Firefox to open webpages in a new tab when selected from the tab in use.

"SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. (Error code: ssl_error_weak_server_ephemeral_dh_key) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem." The page used to load in a new tab before I selected to Refresh Firefox. I cannot find out how to allow Firefox to open webpages in a new tab when selected from the tab in use.

Solution choisie

hi, this means that the webserver you're trying to reach is vulnerable to the recently published logjam vulnerability: http://arstechnica.com/security/2015/05/https-crippling-attack-threatens-tens-of-thousands-of-web-and-mail-servers/ please report that to webmaster of the site in question to fix that issue...

Lire cette réponse dans son contexte 👍 29

Toutes les réponses (10)

more options

Solution choisie

hi, this means that the webserver you're trying to reach is vulnerable to the recently published logjam vulnerability: http://arstechnica.com/security/2015/05/https-crippling-attack-threatens-tens-of-thousands-of-web-and-mail-servers/ please report that to webmaster of the site in question to fix that issue...

more options

Workaround for Firefox 39 and above:

1) In FireFox, enter "about:config" in the URL field and press enter. 2) Accept the "This might void your warranty!" warning :) 3) In the search field at the top, enter "security.ssl3.dhe_rsa_aes" 4) Double click each result (128 and 256) to toggle the Value to "false"

Now retry your site - it should work now. Remember to change these settings back when you're done.

more options

higherdestiny: lifesaver - thank you :)

more options

@higherdestiny: Your solution worked but are there any cons to it?

Thanks

more options

By re-enabling these DHE cipher suites you will make yourself vulnerable to the Logjam attack.

more options

Except any other way to do this about:config ? i mean in programmatically

more options

You can only do that via the about:config page, but enabling these two cipher suites is not recommended. You should contact the website and ask them to upgrade their security.

Logjam: How Diffie-Hellman Fails in Practice:


Users of Firefox releases 38 and older can disable these cipher suites and toggle these prefs to false via this extension:

more options

This is not always possible. In my case, the webpage is served by a legacy PCI raid card - I very much doubt the manufacturer will be doing any updates. My only option (if I want to carry on using Firefox!) is to drop the shields, inspect the raid status etc, then raise the shields again. I just hope there are no Klingons about!

Can anyone suggest any other solutions?

more options

Thanks for help!

Modifié le par rubone

more options

Peter said

This is not always possible. In my case, the webpage is served by a legacy PCI raid card - I very much doubt the manufacturer will be doing any updates. My only option (if I want to carry on using Firefox!) is to drop the shields, inspect the raid status etc, then raise the shields again. I just hope there are no Klingons about! Can anyone suggest any other solutions?

I would like to hear other suggestions for this as well. I have a couple of internal sites. I used to be able to create an exception for _that_ specific site, without disabling all security, after accepting a number of warnings etc. Now I have to use a different browser.