Skip to content

Commit

Permalink
Add files via upload
Browse files Browse the repository at this point in the history
  • Loading branch information
map17018 authored Oct 18, 2021
1 parent 49c0f1b commit 64b5bd7
Show file tree
Hide file tree
Showing 2 changed files with 27 additions and 0 deletions.
Binary file added Deisgn Proposal_ Monitor Flowchart .pdf
Binary file not shown.
27 changes: 27 additions & 0 deletions Deisgn Proposal_ Monitor Flowchart .txt
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

0 comments on commit 64b5bd7

Please sign in to comment.