We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

TLS v1.2 ciphers

  • 3 件の返信
  • 1 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: cor-el

nitinchawla
nitinchawla
more options

Hi,

I am working with one of our customer who is using TLS v1.2 and these ciphers: AES256-GCM-SHA384 AES256-SHA256 AES128-GCM-SHA256 AES128-SHA256

These ciphers are supported by Chrome and Safari and we are wondering when firefox is planning to support it?

Thanks!

Hi, I am working with one of our customer who is using TLS v1.2 and these ciphers: AES256-GCM-SHA384 AES256-SHA256 AES128-GCM-SHA256 AES128-SHA256 These ciphers are supported by Chrome and Safari and we are wondering when firefox is planning to support it? Thanks!

すべての返信 (3)

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

Planning? We should already support it since years.

James
James
  • Moderator
  • Top 10 Contributor
more options

Firefox has supported TLS 1.2 by default since Firefox 27.0 Release (Feb 4, 2014) as per Bug#861266. It can support TLS 1.3 but still not enabled by default.

There are TLS settings prefs on the about:config page that specify the minimum and maximum TLS version.

  • security.tls.version.min = 1
  • security.tls.version.max = 3

1 means TLS 1.0 2 means TLS 1.1 3 means TLS 1.2 (default) 4 means TLS 1.3;

この投稿は James により に変更されました

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

I see these ssl3.*gcm prefs on the about:config page.

security.ssl3.ecdhe_ecdsa_aes_256_gcm_sha384 security.ssl3.ecdhe_ecdsa_aes_128_gcm_sha256 security.ssl3.ecdhe_rsa_aes_256_gcm_sha384 security.ssl3.ecdhe_rsa_aes_128_gcm_sha256