docs: Rewrote most of the developer's guide for clarity
Change-Id: I88fa27898cf3c7be7b93403cc879addbdf04db4c
diff --git a/security.tex b/security.tex
index cffe4c7..e26d5d9 100644
--- a/security.tex
+++ b/security.tex
@@ -54,9 +54,10 @@
\subsection{Certificate Publishing}
-In a network, every router should have the root certificate configured as a trust anchor for the \texttt{validator} in the configuration file.
+In a network, every router must have the root certificate configured as a trust anchor for the \texttt{validator} in the configuration file. If two routers in a network do not share a common trust anchor, then when one seeks to validate the data of the other, they may be unable to establish trust in their signature. This is, of course, because of how the trust hierarchy is set up: you trust the person that signed some router's certificate, because it was signed by the site certificate, and the site certificate was signed by the region, etc., and the $nth$ certificate was signed by the root certificate, which is your trust anchor, so you ``just trust it''. Moreover, if your trust anchor is \emph{before} their trust anchor in the ``chain'', then they will be able to trust you, but you will not be able to trust them.
+
For each site, at least one router should publish the site certificate, and at least one router should publish the certificate of the site operator.
-Each router should publish its own certificate.
+Each router should publish its own certificate. This is a matter of performance; a network would work if all certificates for all nodes were kept centrally, but distributing the certificates in this way improves performance.
All this information must be explicitly specified in the configuration file.
For example, the following configuration file indicates that NLSR should publish the site certificate and the router certificate:
@@ -73,4 +74,4 @@
cert-to-publish "$SITE_CERT_OUTPUT_FILE" ; name of the router certificate file
...
}
-\end{verbatim}
\ No newline at end of file
+\end{verbatim}