Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Avatar for Username

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

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

SSL connection error since update of firefox

  • 1 réponse
  • 4 ont ce problème
  • 1 vue
  • Dernière réponse par cor-el

iamsbee
iamsbee
more options

Since upgrading to firefox 37, navigating to URL www.jncb.com/internetbanking.php?RetailLogin results in the error below being displayed:

Secure Connection Failed

An error occurred during a connection to retail.ncbelink.com. SSL received a record with an incorrect Message Authentication Code. (Error code: ssl_error_bad_mac_read)

I am a member of staff at the company that runs the website and seeking ant clues as to what is required to resolve the issue permanently for users.

Since upgrading to firefox 37, navigating to URL www.jncb.com/internetbanking.php?RetailLogin results in the error below being displayed: Secure Connection Failed An error occurred during a connection to retail.ncbelink.com. SSL received a record with an incorrect Message Authentication Code. (Error code: ssl_error_bad_mac_read) I am a member of staff at the company that runs the website and seeking ant clues as to what is required to resolve the issue permanently for users.

Toutes les réponses (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

The website may try to fallback to TLS 1.0 in a way that is no longer allowed in current releases.

  • Connection Encrypted (TLS_RSA_WITH_AES_256_CBC_SHA, 256 bit keys, TLS 1.0)

You can open the about:config page via the location/address bar and use its search bar to locate this pref:

  • security.tls.insecure_fallback_hosts

You can double-click the line to modify the pref and add the domain to this pref. If there are already websites (domains) in this list then add a comma and the new domain (no spaces). You should only see domains separated by a comma in the value column.

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.