diff options
Diffstat (limited to 'summary/src/lwm/src/conclusion.tex')
| -rw-r--r-- | summary/src/lwm/src/conclusion.tex | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/summary/src/lwm/src/conclusion.tex b/summary/src/lwm/src/conclusion.tex new file mode 100644 index 0000000..e071935 --- /dev/null +++ b/summary/src/lwm/src/conclusion.tex @@ -0,0 +1,15 @@ +\section{Conclusion} \label{lwm:sec:conclusion} +We proposed a backwards-compatible CT/bis extension that enables light-weight +monitoring (in short LWM). At the cost of a few hundred Kb per day, a subject +can either self-monitor or subscribe to verifiable certificate notifications for +a dozen of logs via an untrusted notifier. The security of LWM piggybacks on the +gossip-audit model of CT, and it relies only on the existence of at least one +honest monitor that verifies our extension. The cost of a compliant log is +overhead during the tree head construction, and this overhead is insignificant +in comparison to a log's STH frequency. A notifier can generate verifiable +certificate notifications---even for wild-card queries for all domains under a +top-level domain---in the order of milliseconds on a single core. Given an +STH frequency of one hour and 288~M LWM subjects, the incurred bandwidth +overhead is roughly 640~Mbps for proofs. As such, a log could easily be its +own notifier on a 1~Gbps connection. Further, any willing third-party could +notify for a dozen of logs on a 10~Gbps connection. |