Remove Symantec Certificate Transparency log
Reported by
vaclav.j...@gmail.com,
Nov 19
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Steps to reproduce the problem: 1. open RFC's get-sth endpoint: https://symantec.ct.googleapis.com/ct/v1/get-sth What is the expected behavior? server should respond according to RFC or server should be marked with attribute 'disqualified_at' What went wrong? Server doesn't respond but it's included in list of CT compliant logs (in Chrome) Did this work before? N/A Chrome version: 70.0.3538.102 Channel: stable OS Version: 10.0 Flash Version: "description": "Symantec log", "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEluqsHEYMG1XcDfy1lCdGV0JwOmkY4r87xNuroPS2bMBTP01CEDPwWJePa75y9CrsHEKqAy8afig1dpkIPSEUhg==", "url": "ct.ws.symantec.com/", "maximum_merge_delay": 86400, "operated_by": [ 2 ], "dns_api_endpoint": "symantec.ct.googleapis.com" }
,
Nov 19
,
Nov 19
Redirecting to asymmetric@ for Triage.
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
||||
►
Sign in to add a comment |
||||
Comment 1 by drubery@chromium.org
, Nov 19Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Type-Bug
Owner: rsleevi@chromium.org