We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For analysis of future security incidents, it would be good if we store the full certificate PEM once for each fingerprint seen.
This would be pretty easy to add using a second table that contains two columns: fingerprint, PEM.
Note: we should move certificate data to its own database table ( #30 ) before storing additional data.
The text was updated successfully, but these errors were encountered:
This would also help us track whether sites are using certs that e.g. are signed by different CAs over time.
Sorry, something went wrong.
No branches or pull requests
For analysis of future security incidents, it would be good if we store the full certificate PEM once for each fingerprint seen.
This would be pretty easy to add using a second table that contains two columns: fingerprint, PEM.
Note: we should move certificate data to its own database table ( #30 ) before storing additional data.
The text was updated successfully, but these errors were encountered: