You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2023. It is now read-only.
NOTE: this is not a resource that is meant to be used directly by applications, and is mostly a part of the Chrome CT implementation, we provided a notification as best we could, but ultimately in a best effort manner (developers using this should have a close relationship with the CT ecosystem, as a minimum, following the ct-policy mailing list very carefully: https://groups.google.com/a/chromium.org/g/ct-policy)
The text was updated successfully, but these errors were encountered:
Thanks for the note! I think the best course of action for this is to archive the repo for now, as ct-logs is not an important piece of the rustls ecosystem at the current time. But in the future if we integrate CT checking into webpki, that would change.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I can't tell if this is being used anymore, but the urls in here are very out of date
https://github.com/rustls/ct-logs/blob/main/build.py#L33-L34
https://www.gstatic.com/ct/log_list/log_list.json has not been available for months
it is recommended you update to v3 log lists (v1 is turned down and v2 will be turned down soon): https://groups.google.com/a/chromium.org/g/ct-policy/c/zejEtWAJtEA
update the generator to generate code to use https://www.gstatic.com/ct/log_list/v3/log_list.json and https://www.gstatic.com/ct/log_list/v3/log_list.sig
NOTE: this is not a resource that is meant to be used directly by applications, and is mostly a part of the Chrome CT implementation, we provided a notification as best we could, but ultimately in a best effort manner (developers using this should have a close relationship with the CT ecosystem, as a minimum, following the ct-policy mailing list very carefully: https://groups.google.com/a/chromium.org/g/ct-policy)
The text was updated successfully, but these errors were encountered: