From 26af85967ce063528b4e2498666c724e7c35cb1a Mon Sep 17 00:00:00 2001 From: Millenia A Polanco Date: Mon, 18 Oct 2021 14:48:51 -0400 Subject: [PATCH] Delete Deisgn Proposal_ Monitor Flowchart .txt --- Deisgn Proposal_ Monitor Flowchart .txt | 27 ------------------------- 1 file changed, 27 deletions(-) delete mode 100644 Deisgn Proposal_ Monitor Flowchart .txt diff --git a/Deisgn Proposal_ Monitor Flowchart .txt b/Deisgn Proposal_ Monitor Flowchart .txt deleted file mode 100644 index 3fa8138..0000000 --- a/Deisgn Proposal_ Monitor Flowchart .txt +++ /dev/null @@ -1,27 +0,0 @@ -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 \ No newline at end of file