Andrew Ayer 30d171343a Add -start_at_end option to begin monitoring logs at the end ... When Cert Spotter starts monitoring a log that it has never monitored before, it can either start monitoring it from the beginning, or seek to the end and start monitoring there. Monitoring from the beginning guarantees detection of all certificates, but requires downloading hundreds of millions of certificates, which takes days. With the new -start_at_end option, you can save significant time by starting at the end. You will miss certificates that were added to a log before Cert Spotter starts monitoring it, but you can always use the Cert Spotter API <https://sslmate.com/certspotter/api> or crt.sh to find them. Previously, the -start_at_end behavior was implied the first time you ever ran Cert Spotter. This is no longer the case.		2019-12-03 11:12:40 -05:00
..
certspotter	changed bygonessl behavior	2018-07-19 16:12:17 -07:00
ctparsewatch	Run gofmt	2016-07-28 14:55:46 -04:00
submitct	Add functions to verify SCTs	2017-12-17 09:51:46 -08:00
common.go	Add -start_at_end option to begin monitoring logs at the end	2019-12-03 11:12:40 -05:00
helpers.go	Overhaul log processing and auditing	2017-01-05 21:00:35 -08:00
log_state.go	Apply gofmt	2017-01-08 10:17:00 -08:00
state.go	Use a lock file to prevent certspotter from running concurrently	2017-01-10 10:50:41 -08:00