Questo sito potrebbe offrire funzionalità limitate durante le operazioni di manutenzione per migliorare l'esperienza utente. Se un articolo non risolve il tuo problema e vuoi richiedere supporto, la nostra comunità di supporto è pronta ad aiutarti tramite @FirefoxSupport su Twitter e /r/firefox su Reddit.

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

connecting to a server with a weak key.

  • 4 risposte
  • 5 hanno questo problema
  • 3 visualizzazioni
  • Ultima risposta di balon

more options

I have an old https iternal server. in nightly I get the error The server certificate included a public key that was too weak. (Error code: ssl_error_weak_server_cert_key)

in the release version I get a message stating "This Connection is Untrusted" anf I can continue if I click "I understand the risks"

I understand the minimum requirements for secure connection have benn changed. how can i connect to the site anyway?

I have an old https iternal server. in nightly I get the error The server certificate included a public key that was too weak. (Error code: ssl_error_weak_server_cert_key) in the release version I get a message stating "This Connection is Untrusted" anf I can continue if I click "I understand the risks" I understand the minimum requirements for secure connection have benn changed. how can i connect to the site anyway?

Tutte le risposte (4)

more options

Any luck in adding the host to security.tls.insecure_fallback_hosts ?

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 full domain to the value of this pref. If there are already websites (domains) in this list then add a comma and the new domain (no spaces). There should only be domains separated by a comma in the Value column (example.com,www.example.com).


more options

hi, thanks for the reply.

still no luck. do I have to restart firefox before trying again? I am using the nightly channel ( x64) could it be that the algorithm in question have been removed from the build?

more options

You can check what cipher suite and TLS version is used in older Firefox versions and check if the used cipher suite prefs are still present in about:config. The list of available cipher suites gets shorter and shorter with each release as vulnerable suite are removed.

See also:

more options

form what I see with this addon the server in question have a certificate with signature MD5/RSA with key of 512 bits only. another server with SHA/RSA and 1024 bits key is OK. I could not find in about config a way to set the minimum key length or to enable MD5.