Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër
Solved Arkivuar

Browser still uses TLS_AES_128_GCM_SHA256 (0x1301) 128-bit SSL encryption cipher even when disabled in about:config

cor-el replied
user1555634

Even after disabling all the 128-bit cipher suites in about:config, the cipher TLS_AES_128_GCM_SHA256 (0x1301) is still being used.

I used Qualys SSL Labs Client Test (https://www.ssllabs.com/ssltest/viewMyClient.html), and saw that TLS_AES_128_GCM_SHA256 (0x1301) remains to be the most preferred cipher suite.

All TLS 1.3 connections, such as facebook.com and cloudflare.com, uses that particular AES-128 cipher suite.

Is this a feature or a bug?

Even after disabling all the 128-bit cipher suites in about:config, the cipher TLS_AES_128_GCM_SHA256 (0x1301) is still being used. I used Qualys SSL Labs Client Test (https://www.ssllabs.com/ssltest/viewMyClient.html), and saw that TLS_AES_128_GCM_SHA256 (0x1301) remains to be the most preferred cipher suite. All TLS 1.3 connections, such as facebook.com and cloudflare.com, uses that particular AES-128 cipher suite. Is this a feature or a bug?

Krejt Përgjigjet (1)

Zgjidhja e Zgjedhur

See:

  • Bug 1490902 - TLS 1.3 Adds & Prioritizes 3 Cipher Suites with inferior security to TLS 1.2 Suites

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)