Dave

@kuba I'm certainly open to moving to some other method of grabbing certificates if it's better, more maintainable, etc. The main problem I run into right now is that the...

An interesting post here about not actually using a time value for the 'time' field in ClientHello, but rather more random data. http://security.stackexchange.com/questions/85082/do-chrome-and-firefox-send-random-values-rather-than-the-actual-timestamp-in-cli

In my test with a copy of notary1's data this shrunk the database size by 66%. This would also allow us to properly store other information about certificates, as mentioned...

Leaving this until we have implemented TLS functionality may be nice, as then the existing v2 notaries could be upgraded with only one set of table changes. They could then...

As per #19, if we plan to implement https mostly by using another server in front of cherrypy, then waiting for HTTPS functionality before we change the database structure isn't...

Hey afunix, If you do a direct query to your database after the scanner runs, does the database show updated data? The scanner actually updates data directly inside the database....

Hey, yes, I meant flushing the memcached instance to get rid of notary entries. If you're tracking other data in the cache besides notary results I don't know of an...

Apparently the hex contstants in ssl_scan_sock.py may be raw captures from a Wireshark trace. We may be able to trace a client hello with a newer version of openssl, or...

While working on this a long while back I found a number of things that should be fixed. Created #45 to track it all.

This is probably a duplicate of #20