This repository was archived by the owner on Sep 17, 2021. It is now read-only.
Better handle bad IAM SSL certificates #413
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…to the DB for later analysis.
This was referenced Sep 19, 2016
Merged
kyleberry
pushed a commit
to kyleberry/security_monkey
that referenced
this pull request
Sep 21, 2016
* Added error handling for invalid certs * Adding a call to slurp_exception, which itself records the exception to the DB for later analysis.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an extension to #396.
@markofu added per-certificate error handling. I've taken that and added a call to
slurp_exception, which itself will callstore_exception, so exceptions can be analyzed by querying the database in addition to checking the logs.