Issue 481292 in chromium: ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY in Fedora

[chro...@googlecode.com]

Status: Untriaged
Owner: b...@chromium.org
Labels: Type-Bug Pri-2 Cr-Internals-Network-HTTP2 OS-Linux
Cr-Internals-Network-SSL

New issue 481292 by bem...@chromium.org:
ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY in Fedora
https://code.google.com/p/chromium/issues/detail?id=481292

On Fedora 18 (which is old), I'm seeing this error in Chrome 44 (dev
channel) when trying to access _any_ Google page. Judging by chrome:flags,
SPDY/4 is not enabled.

This seems to be a reappearance of issue 436835.

The system's installed version of NSS is 3.15.2

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: Assigned
Cc: davi...@chromium.org
Labels: Needs-Feedback

Comment #1 on issue 481292 by b...@chromium.org:

ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY in Fedora
https://code.google.com/p/chromium/issues/detail?id=481292

Thank you for filing this bug, for digging up the duplicate, and for
reporting your NSS version. Unfortunately the chrome://flags flag on
HTTP/2 is obsolete. Please open chrome://net-internals/#http2 and look
for "HTTP/2 Enabled" on the top of the page to see whether you are using
HTTP/2.

Could you please restart your browser with --enable-npn-http flag? That
should disable HTTP/2. Please let us know if you can open Google pages
that way.

David: how can one check what ciphersuites are offered in the TLS
handshake, and which one is negotiated? HTTP/2 throws this error because
the negotiated one is not adequate, but NSS 3.15.2 should support AES-GCM.
[1] Thanks.

[1]
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.15.2_release_notes