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.

Sign up for GitHub

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

Jump to bottom

What's the current state of explicit key untrust in certificate stores? #178

Open
adamdecaf opened this issue Mar 3, 2018 · 0 comments
Open

What's the current state of explicit key untrust in certificate stores? #178

adamdecaf opened this issue Mar 3, 2018 · 0 comments
Labels
question
Milestone
0.3.0

Comments

@adamdecaf
Copy link
Owner

I was thinking about implementing #166 and reading the chromium blacklist about the case of sslip.io. It got me thinking.

What's the current state of revoking a public (or private) key in certificate stores? Can all stores even handle a key being deliberately marked as untrusted? Let's investigate that.
@adamdecaf adamdecaf added this to the 0.3.0 milestone Mar 3, 2018
@adamdecaf adamdecaf changed the title question: What's the current state of explicit key untrust in certificate stores? What's the current state of explicit key untrust in certificate stores? Mar 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
0.3.0
Development

No branches or pull requests
1 participant
@adamdecaf