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

Doesn't capture EV bits specific to Chrome #69

Open
konklone opened this issue Mar 25, 2018 · 2 comments
Open

Doesn't capture EV bits specific to Chrome #69

konklone opened this issue Mar 25, 2018 · 2 comments

Comments

@konklone
Copy link
Contributor

Chrome sets its own EV bits, separate from the OS' underlying trust store. This isn't captured anywhere in tl-create. It may or may not be desired to do so, but I at least wanted to note it.

@rmhrisk
Copy link
Contributor

rmhrisk commented Mar 25, 2018

Would love to do this but to do so would require parsing Chrome source and I think it wouldn't be that reliable.

That said, happy to take a PR.

@rmhrisk rmhrisk closed this as completed Mar 25, 2018
@fotisl
Copy link
Contributor

fotisl commented Mar 26, 2018

I would just like to note that tl-create is already parsing HTML for apple, so I don't think that parsing C source is bad as a practice.
I have looked at this in the past, and the only issue I can think of is that we would just fetch the EV CAs which is not consistent with the rest of the trust stores. However, since google chrome doesn't maintain a full trust store I don't think there is a real problem here.
I would be glad to implement this when I find some time.

@rmhrisk rmhrisk reopened this Mar 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants