-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
27 additions
and
0 deletions.
There are no files selected for viewing
Binary file not shown.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
Monitor | ||
|
||
|
||
________________ | ||
|
||
|
||
|
||
|
||
Monitor | ||
Monitor Options: | ||
* CertSpotter: | ||
* Pros: We have it running, least complex of the options | ||
* Cons: No Gossip implemented, likely doesn’t follow official CT standards | ||
|
||
|
||
* Monologue | ||
* Pros: Most Fleshed out of the three options | ||
* Cons: Seems like a Minimum Viable Product, and thus has the least documentation/explanations. TODO messages in the code | ||
* CTClient.go | ||
* Pros: Simple, clear functions for interaction with loggers | ||
* Cons: Will require building monitor from scratch, which could be significantly more work that the other 2 options | ||
|
||
|
||
We will likely be implementing a combination of these as needed. We will use CTClient.go as a baseline and add in functionality from other monitor implementations should we find any gaps. This will also involve creating a formal monitor of our own which performs the loop outlined in the monitor flowchart and interacts with the logger on our local machine. | ||
|
||
|
||
To start, we will be using the google API for certificate transparency found at https://ct.googleapis.com/. This follows the IETF CTv1 |