X
モバイル版サイトに移動するには、ここをタップします。

サポートフォーラム

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

Behavior for security.tls.version.fallback, max and min

投稿日時

Hi folks, I have a question about this combination in config: security.tls.version.fallback-limit = 3

security.tls.version.max = 3

security.tls.version.min = 1

All of those are default in FF 48.0.2 .

According to KB, FF should allow TLS 1.0, 1.1 and 1.2, and fallback is not allowed from TLS 1.2.

Here is my question: if the server only supports TLS 1.0, what will FF do? Refuse it or happily connect to the server?

Hi folks, I have a question about this combination in config: security.tls.version.fallback-limit = 3 security.tls.version.max = 3 security.tls.version.min = 1 All of those are default in FF 48.0.2 . According to KB, FF should allow TLS 1.0, 1.1 and 1.2, and fallback is not allowed from TLS 1.2. Here is my question: if the server only supports TLS 1.0, what will FF do? Refuse it or happily connect to the server?

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

選ばれた解決策

Firefox 48 can connect with servers that only advertise support for TLS 1.0 (assuming they use a valid certificate and ciphers that Firefox considers acceptable).

"Fallback" is a process where the server advertises support for TLS 1.2 but Firefox is unable to connect using TLS 1.2 for some reason, so Firefox used to try TLS 1.1, 1.0, even SSLv3. Since that kind of fallback can be triggered by an untrusted intermediary, it is no longer supported.

この回答をすべて読む 3

システム詳細の追加情報

アプリケーション

  • ユーザーエージェント: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

詳細情報

jscher2000
  • Top 10 Contributor
解決数 8693 件 回答数 71058 件
投稿日時

選ばれた解決策

Firefox 48 can connect with servers that only advertise support for TLS 1.0 (assuming they use a valid certificate and ciphers that Firefox considers acceptable).

"Fallback" is a process where the server advertises support for TLS 1.2 but Firefox is unable to connect using TLS 1.2 for some reason, so Firefox used to try TLS 1.1, 1.0, even SSLv3. Since that kind of fallback can be triggered by an untrusted intermediary, it is no longer supported.

Firefox 48 can connect with servers that only advertise support for TLS 1.0 (assuming they use a valid certificate and ciphers that Firefox considers acceptable). "Fallback" is a process where the server advertises support for TLS 1.2 but Firefox is unable to connect using TLS 1.2 for some reason, so Firefox used to try TLS 1.1, 1.0, even SSLv3. Since that kind of fallback can be triggered by an untrusted intermediary, it is no longer supported.

役に立った返信

jscher2000 said

Firefox 48 can connect with servers that only advertise support for TLS 1.0 (assuming they use a valid certificate and ciphers that Firefox considers acceptable). "Fallback" is a process where the server advertises support for TLS 1.2 but Firefox is unable to connect using TLS 1.2 for some reason, so Firefox used to try TLS 1.1, 1.0, even SSLv3. Since that kind of fallback can be triggered by an untrusted intermediary, it is no longer supported.

Thank you for explaining fallback. I got some misunderstanding on that word :/

I will promote the answer a bit later since I am busy now.

Thanks again!

''jscher2000 [[#answer-916540|said]]'' <blockquote> Firefox 48 can connect with servers that only advertise support for TLS 1.0 (assuming they use a valid certificate and ciphers that Firefox considers acceptable). "Fallback" is a process where the server advertises support for TLS 1.2 but Firefox is unable to connect using TLS 1.2 for some reason, so Firefox used to try TLS 1.1, 1.0, even SSLv3. Since that kind of fallback can be triggered by an untrusted intermediary, it is no longer supported. </blockquote> Thank you for explaining fallback. I got some misunderstanding on that word :/ I will promote the answer a bit later since I am busy now. Thanks again!