New issue
Advanced search Search tips

Issue 628030 link

Starred by 2 users
Status: WontFix
Owner:
nhar...@chromium.org
Closed: Jul 2017
Cc:
eroman@chromium.org
mmenke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Add Channel ID logging for QUIC connections

Project Member Reported by nhar...@chromium.org, Jul 13 2016 
For TLS connections, the Channel ID Service, Store, whether it's ephemeral, and the key used are logged to the SOCKET source in net-internals if channel ID was sent for that connection. A QUIC_SESSION source doesn't have any of this logging (and doesn't use a TLS connection) - some sort of equivalent logging should be added.
Project Member

Comment 1 by sheriffbot@chromium.org, Jul 14 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by nhar...@chromium.org, Jul 14 2017

Status: WontFix (was: Untriaged)
Once Token Binding is shipped and Channel ID is removed, this bug will be irrelevant. I don't think I'll get around to doing this, and moving from QUIC crypto to TLS in QUIC will force turning down Channel ID.
►

Sign in to add a comment