Introducing TLSChronicle: A cutting-edge project that collects and logs TLS certificates multiple times to prove continuous website connections over time. Ensure secure, verifiable proof of your online presence. Ideal for compliance, monitoring, and security auditing. #TLS #ETH
TLSCertChronicle is a plugin adapted from the twitter plugin example of the TLSNotary project, designed to log & notarize TLS (Transport Layer Security) certificates multiple times.
The plugin is a proof of concept for demonstrating connections to specific websites over time.
This is a mechanism for demonstrating ongoing access, which is essential for compliance, monitoring, and security auditing purposes.
In the context of DataDAOs where physiological user data is collected and users want to enrich the value of their data, they could use TLSCertChronicle to provide further proof that they accessed a website during a specific interval, supported by the certificates.
The project is a plugin adapted from the boilerplate Twitter user profile example. For it, I used the TLSNotary extension and followed their guide. I edited the Twitter plugin using JavaScript/TypeScript to make multiple certificate requests/notarizings instead of a single one.
For my solo hacking experience, it's worth mentioning that I:
setInterval
, timeout
, or JavaScript methods due to import issues/lack of skill by using a decreasing counter to wait between requests before collecting credentials again
The purpose of using a decreasing counter was to avoid downloading certificates instantly one after the other, which would make the first one visible too quickly.