|
|
Chromium Code Reviews|
Created:
4 years, 6 months ago by Eran Messeri Modified:
4 years, 6 months ago Reviewers:
eroman CC:
chromium-reviews, 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. |
DescriptionCertificate Transparency: Adding CNNIC's CT log server.
Said log has been pending inclusion since February 26th, 2016, and
has complied with the requirements for inclusion.
BUG=583208
Committed: https://crrev.com/3a79a2a6429d0adf9d03cd37e3da2850869d4fa6
Cr-Commit-Position: refs/heads/master@{#396817}
Patch Set 1 #
Messages
Total messages: 15 (5 generated)
Description was changed from ========== Certificate Transparency: Adding CNNIC's CT log server. Said log has been pending inclusion since February 26th, 2016, and has complied with the requirements for inclusion. BUG=583208 ========== to ========== Certificate Transparency: Adding CNNIC's CT log server. Said log has been pending inclusion since February 26th, 2016, and has complied with the requirements for inclusion. BUG=583208 ==========
eranm@chromium.org changed reviewers: + eroman@chromium.org
Eric, a small change to the CT log list for you to review, as you've just reviewed another change to it.
lgtm
Thinking out loud: It may be useful to have some documentation for each log pointing to the process of how it was added -- in this case, just link to the crbug.com/ issue for adding CNNIC. Or if there is a document or authoritative registry maintained somewhere else that justifies the log list.
> It may be useful to have some documentation for each log pointing to the process > of how it was added -- in this case, just link to the crbug.com/ issue for > adding CNNIC. Do you mean documentation internally? That's what blame is for. I'm not sure I get what you're getting at.
There is a policy for including CT log servers no? Why not then include details for inclusion beside the entry, rather than spelunking through git blame to maybe find it. As a reader I would appreciate seeing the reason for things inline, rather than an undocumented blob of data.
On 2016/05/30 21:52:59, eroman wrote: > There is a policy for including CT log servers no? > > Why not then include details for inclusion beside the entry, rather than > spelunking through git blame to maybe find it. > > As a reader I would appreciate seeing the reason for things inline, rather than > an undocumented blob of data. That's a good point - currently we do not export externally-visible data about logs' compliance status. We're working on a new dashboard with data we could export. In the meanwhile, I'll send the link internally.
The CQ bit was checked by eranm@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2011313002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/2011313002/1
Message was sent while issue was closed.
Description was changed from ========== Certificate Transparency: Adding CNNIC's CT log server. Said log has been pending inclusion since February 26th, 2016, and has complied with the requirements for inclusion. BUG=583208 ========== to ========== Certificate Transparency: Adding CNNIC's CT log server. Said log has been pending inclusion since February 26th, 2016, and has complied with the requirements for inclusion. BUG=583208 ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from ========== Certificate Transparency: Adding CNNIC's CT log server. Said log has been pending inclusion since February 26th, 2016, and has complied with the requirements for inclusion. BUG=583208 ========== to ========== Certificate Transparency: Adding CNNIC's CT log server. Said log has been pending inclusion since February 26th, 2016, and has complied with the requirements for inclusion. BUG=583208 Committed: https://crrev.com/3a79a2a6429d0adf9d03cd37e3da2850869d4fa6 Cr-Commit-Position: refs/heads/master@{#396817} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/3a79a2a6429d0adf9d03cd37e3da2850869d4fa6 Cr-Commit-Position: refs/heads/master@{#396817}
Message was sent while issue was closed.
Thanks for the background Eran. Having some extra comments here in the future would be appreciated. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
