Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1404067 - ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for amazon.com and others
Summary: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for amazon.com and others
Keywords:
Status: CLOSED DUPLICATE of bug 1403611
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 01:05 UTC by Miro Hrončok
Modified: 2016-12-14 08:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-14 08:52:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2016-12-13 01:05:03 UTC
Description of problem:
Sites with Symantec cert are not working.

See https://bugs.chromium.org/p/chromium/issues/detail?id=664177


Version-Release number of selected component (if applicable):
chromium-54.0.2840.90-3.fc25.x86_64

Steps to Reproduce:
1. Go to www.amazon.com in Chromium (actually any site using Symantec cert)

Actual results:
Broken HTTPS, NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

Expected results:
The HTTPS is fine, should display the site.

Additional info:
I'm unsure from the above linked issue comments whether it should have been fixed in 54, but I'm running 54 and apparently it doesn't work for me. There are some commits referenced there, so maybe we could backport those? Nevertheless Chromium 55 should fix this.

Comment 1 Miro Hrončok 2016-12-14 08:52:17 UTC

*** This bug has been marked as a duplicate of bug 1403611 ***


Note You need to log in before you can comment on or make changes to this bug.