You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by bu...@apache.org on 2011/12/26 13:14:29 UTC
svn commit: r801043 - /websites/staging/river/trunk/content/wot.html
Author: buildbot
Date: Mon Dec 26 12:14:29 2011
New Revision: 801043
Log:
Staging update by buildbot
Modified:
websites/staging/river/trunk/content/wot.html
Modified: websites/staging/river/trunk/content/wot.html
==============================================================================
--- websites/staging/river/trunk/content/wot.html (original)
+++ websites/staging/river/trunk/content/wot.html Mon Dec 26 12:14:29 2011
@@ -67,7 +67,7 @@
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
<h1 id="web_of_trust">Web of trust</h1>
-<p>[http://en.wikipedia.org/wiki/Web_of_trust]</p>
+<p><a href="http://en.wikipedia.org/wiki/Web_of_trust">http://en.wikipedia.org/wiki/Web_of_trust</a></p>
<p>Gregg: </p>
<p>... Ultimately, Jini needs, in my opinion, to focus authentication above the network layer, and use signed jars, encrypted paths, and cert based auth, so that the network path, can not be a part of the exploitation, and instead, each end of a "communication", is responsible for trusting the other, through negotiations carried through the network, instead of using information about the network to guarantee trust. ...</p>
</div>