Certificate Transparency - Google "argon" Log Servers |
||
Issue descriptionThis bug will be used as an umbrella bug for the temporally sharded Google Argon Certificate Transparency Logs. It is being created at the request of Chrome, who have said they would prefer to track a set of temporally sharded Logs with one bug. The combination of the certificate expiry ranges of the Google Argon Logs allows any certificate that chains to a trusted root and has a lifetime of 27 months or less to be logged to one of the Argon Logs. Further Argon Logs will be turned up in the future in order to maintain the window for accepted certificates. Operator details for the Argon Logs: - Operator: Google - Email: google-ct-logs@googlegroups.com - Persons authorized to represent the Log operator: Al Cutter, Pierre Phaneuf, Paul Hadfield, Martin Smith, Rob Percival, Kat Joyce, David Drysdale, Gary Belvin, Pavel Kalinnikov, Tatiana Merkulova Links to the bugs for the existing Logs: https://ct.googleapis.com/logs/argon2017: https://crbug.com/756813 https://ct.googleapis.com/logs/argon2018: https://crbug.com/756814 https://ct.googleapis.com/logs/argon2019: https://crbug.com/756817 https://ct.googleapis.com/logs/argon2020: https://crbug.com/756818 https://ct.googleapis.com/logs/argon2021: https://crbug.com/756819 All updates for the existing Argon Logs will be posted on this bug from now on. Any new Argon Logs will be announced / will request inclusion on this bug.
,
Oct 15
Could you provide the public key in DER format, as required by Chrome Log Policy (not to mention my monitoring workflow ;-)? Thanks!
,
Oct 16
No problem, I've attached the public key in DER format, as output by the following command: $ openssl pkey -pubin -in argon2022.pem -outform der -out argon2022.der
,
Nov 6
Log Operator phone number pulled from other Google Argon applications: phone number: +442070313000 (Google UK) Argon 2022 application looks good; over to CT Team for monitoring.
,
Nov 9
Thank you for your request, we have started monitoring your Log server. Should no issues be detected, the initial compliance monitoring phase will be complete on Feb 6th 2019 and we will update this bug shortly after that date to confirm. |
||
►
Sign in to add a comment |
||
Comment 1 by robpercival@chromium.org
, Sep 25178 bytes
178 bytes Download