|
|
Created:
4 years, 4 months ago by Rob Percival Modified:
4 years, 3 months ago CC:
chromium-reviews, rsleevi+watch_chromium.org, certificate-transparency-chrome_googlegroups.com, cbentzel+watch_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionAdds WoSign log to CT logs list
It has recently completed its 90d compliance monitoring period.
BUG=605415
Committed: https://crrev.com/64cb9e2a71c89e801d45dc2cb1476305910851f3
Cr-Commit-Position: refs/heads/master@{#414378}
Patch Set 1 #Patch Set 2 : Lowercase hex #Patch Set 3 : Adds WoSign DNS endpoint #Messages
Total messages: 22 (8 generated)
robpercival@chromium.org changed reviewers: + eranm@chromium.org
I've left the DNS endpoint empty for now, as it's going to take some time to get one up and running. Should we hold off on adding it at all until the DNS endpoint is ready?
rsleevi@chromium.org changed reviewers: + rsleevi@chromium.org
Since we said a DNS endpoint was required, it does sound like we should hold off.
How's the DNS coming along? :)
On 2016/08/12 at 19:31:30, rsleevi wrote: > How's the DNS coming along? :) The entire team was on a trip last week, so we made no progress. We'll update this week, but aim to get it ready for m54.
On 2016/08/12 19:31:30, Ryan Sleevi (slow) wrote: > How's the DNS coming along? :) The DNS frontends for WoSign and StartCom are now available. I've added a patch set with the DNS endpoint.
On 2016/08/16 14:20:05, Rob Percival wrote: > On 2016/08/12 19:31:30, Ryan Sleevi (slow) wrote: > > How's the DNS coming along? :) > > The DNS frontends for WoSign and StartCom are now available. I've added a patch > set with the DNS endpoint. Just to confirm: Do the concerns raised in Issue 605415 warrant revisiting this? Happy to discuss on ct-policy@ if you're uncertain.
On 2016/08/16 20:24:33, Ryan Sleevi (slow) wrote: > On 2016/08/16 14:20:05, Rob Percival wrote: > > On 2016/08/12 19:31:30, Ryan Sleevi (slow) wrote: > > > How's the DNS coming along? :) > > > > The DNS frontends for WoSign and StartCom are now available. I've added a > patch > > set with the DNS endpoint. > > Just to confirm: Do the concerns raised in Issue 605415 warrant revisiting this? > Happy to discuss on ct-policy@ if you're uncertain. I don't believe so. As the policy says, a log must "have 99% uptime, with no outage lasting longer than the MMD (**as measured by Google**)" (emphasis added). None of the other logs have been subjected to a requirement that their log be equally accessible via other routes. We may introduce such a requirement in the future but, as of now, that is not the policy. However, if you think a retroactive policy change is called for, feel free to raise it on ct-policy@. On a less policy-focused note, since Chrome receives STHs and inclusion proofs via Google, it is not directly affected by poor connectivity on routes that Google doesn't use.
lgtm
Description was changed from ========== Adds WoSign log to CT logs list It has recently completed its 90d compliance monitoring period. Inclusion request: https://crbug.com/605415 A DNS endpoint for this log will be added once available. BUG=605415 ========== to ========== Adds WoSign log to CT logs list It has recently completed its 90d compliance monitoring period. BUG=605415 ==========
Please make sure to keep the CL description up to date :) Edited to reflect there's a DNS server ;)
The CQ bit was checked by robpercival@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
The CQ bit was checked by robpercival@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Adds WoSign log to CT logs list It has recently completed its 90d compliance monitoring period. BUG=605415 ========== to ========== Adds WoSign log to CT logs list It has recently completed its 90d compliance monitoring period. BUG=605415 ==========
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== Adds WoSign log to CT logs list It has recently completed its 90d compliance monitoring period. BUG=605415 ========== to ========== Adds WoSign log to CT logs list It has recently completed its 90d compliance monitoring period. BUG=605415 Committed: https://crrev.com/64cb9e2a71c89e801d45dc2cb1476305910851f3 Cr-Commit-Position: refs/heads/master@{#414378} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/64cb9e2a71c89e801d45dc2cb1476305910851f3 Cr-Commit-Position: refs/heads/master@{#414378} |