Nightly no longer use TLS 1.3 recently

RESOLVED INVALID

Status

()

Core
Security: PSM
RESOLVED INVALID
2 months ago
2 months ago

People

(Reporter: Gakki, Unassigned)

Tracking

({nightly-community})

Trunk
nightly-community
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

2 months ago
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20171204234137

Steps to reproduce:

I can confirm that TLS1.3 is enabled in about:config in Nightly (20171204234137)


Actual results:

Nightly show me: TLS1.2


Expected results:

It should show as TLS1.3
Hi,

TLS1.3 is enabled in latest Nightly, you can check https://tls13.crypto.mozilla.org/ which should correctly display in Nightly but not in previous versions (like 57).

Can you please detail the issue ?

Comment 2

2 months ago
Bug 1420060?
Status: UNCONFIRMED → NEW
Component: Untriaged → Security: PSM
Ever confirmed: true
Keywords: nightly-community, regression
Product: Firefox → Core
Summary: Nightly don't support TLS 1.3 recently → Nightly no longer use TLS 1.3 recently
Firefox Nightly got updated to version 22 recently. Since most TLS 1.3 servers out there are still on draft 18 it is to expect that TLS 1.3 isn't used. (This is certainly the case for https://imququ.com/.)
Keywords: regression
(Reporter)

Comment 4

2 months ago
(In reply to Franziskus Kiefer [:fkiefer or :franziskus] from comment #3)
> Firefox Nightly got updated to version 22 recently. Since most TLS 1.3
> servers out there are still on draft 18 it is to expect that TLS 1.3 isn't
> used. (This is certainly the case for https://imququ.com/.)

Thank you very much for your answer!
Making "INVALID" which is bugzilla's unfortunate way of saying "expected behavior".
Status: NEW → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.