From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes
Date: Tuesday February 27, 19101 @ 1:02
Author: fen
CVSWEB Options: -------------------
Main CVSWeb: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi
View this module: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes
-----------------------------------
Update of /usr/local/cvs/public/openprivacy/htdocs/notes
In directory giga:/home/fen/projects/openprivacy/htdocs/notes
Modified Files:
whitepaper.shtml
Log Message:
added OP communications
*****************************************************************
File: openprivacy/htdocs/notes/whitepaper.shtml
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/whitepaper.shtml?annotate=1.23
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/whitepaper.shtml?rev=1.23&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/whitepaper.shtml.diff?r1=1.23&r2=1.22
-----------------------------------
Index: openprivacy/htdocs/notes/whitepaper.shtml
diff -u openprivacy/htdocs/notes/whitepaper.shtml:1.22 openprivacy/htdocs/notes/whitepaper.shtml:1.23
--- openprivacy/htdocs/notes/whitepaper.shtml:1.22 Tue Feb 27 00:49:30 2001
+++ openprivacy/htdocs/notes/whitepaper.shtml Tue Feb 27 01:02:44 2001
@@ -9,7 +9,7 @@
</head>
<body bgcolor="#ffffff">
- <!-- $Id: whitepaper.shtml,v 1.22 2001/02/27 08:49:30 fen Exp $ -->
+ <!-- $Id: whitepaper.shtml,v 1.23 2001/02/27 09:02:44 fen Exp $ -->
<h1>OpenPrivacy - Building a Better Internet</h1>
@@ -139,7 +139,7 @@
<h4>Nym Service</h4>
<p>
OpenPrivacy uses a <i>nym service</i> to to create and manage a
- set of pseudonymous virtual users - generaly represented by
+ set of pseudonymous virtual users - generally represented by
public-key pairs - that inhabit OpenPrivacy space. These nyms are
hierarchically organized within the service, so that a few main
(parent) nyms can beget a large number of child nyms and child
@@ -172,10 +172,29 @@
its disposal, such as the reputations of the various local
opinions (and their, recursive, reputations), access to the
opinions of other, remote RCEs, the calculated or gifted bias of
- the requestor, and even hand-tweaking by its human maintainer.
+ the requester, and even hand-tweaking by its human maintainer.
Ultimately, what form its opinions take, their quality and other
factors are judged by its peers who may then assign it a
reputation, and seek its advice -- or not.
+ </p>
+ </blockquote>
+ <h3>OpenPrivacy Communications</h3>
+ <blockquote>
+ <p>
+ We outline a course-grained capability-based framework in which
+ each nexus of reputation services - generally located one to a
+ hardware machine - is considered to be a secure computation
+ environment (or "vat") with respect to itself. <font
+ color=red>[present a simple proof that supports this
+ claim.]</font> Communications between vats is asynchronous and
+ unreliable. Secure streams can be built, analogous to the way in
+ which SSL is implemented on top of TCP, which is in turn
+ implemented on top of UDP, but are not required for operation.
+ While we define the implementation of the communications mechanism
+ to be outside the scope of OpenPrivacy per se, we expect that a
+ secure, anonymous and uncensorable mechanism such as Freenet, Free
+ Haven or Publius would be best suited to the need for robust,
+ distributed and private communications.
</p>
</blockquote>
<h3>Reference Applications</h3>
This archive was generated by hypermail 2b30 : Tue Feb 27 2001 - 01:02:45 PST