Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regular updates #11

Open
jvehent opened this issue Aug 5, 2016 · 4 comments
Open

Regular updates #11

jvehent opened this issue Aug 5, 2016 · 4 comments

Comments

@jvehent
Copy link

jvehent commented Aug 5, 2016

Hi @kirei, thanks a lot for this compilation of truststores! We use it in https://github.com/mozilla/tls-observatory to evaluate certificate trust.
One thing I've been wondering about is the freshness of the data in this repo. The Mozilla CA, for example, is updated monthly upstream but I don't believe this is reflected here. What would it take to have weekly or monthly updates of this repository? Could it be automated somehow?

@jschlyter
Copy link
Member

I believe @leifj has plan to do regular updates.

@leifj
Copy link

leifj commented Aug 17, 2016

Adding @br00k - we have been talking about this as an extension to TACAR and other GEANT trust store activities.

@secworks
Copy link
Contributor

You pull manually right now, correct? We can at least set a reminder that we should update once a month.

@jvehent
Copy link
Author

jvehent commented Dec 2, 2016

I'm taking a different approach. Mozilla's Root CA Program is working on a Common CA Database managed in Salesforce. The database exports CSV files that contain the latest list of trusted CA for Mozilla and Microsoft. I am told that other organizations may join the effort in the future.

That means retrieving a truststore can be done directly from these exports. I wrote a small Go script that does so: https://github.com/mozilla/tls-observatory/blob/master/tools/retrieveTruststoreFromCADatabase.go

It's not always the same data as the one shipped in NSS, or Windows, as there may be a delay between something changing in the upstream CA database and the change being shipped to products. Regardless, that's the data source Mozilla's TLS Observatory will use from now on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants