CVS update: openprivacy/htdocs

From: cvs@openprivacy.org
Date: Tue Feb 06 2001 - 18:53:11 PST

  • Next message: cvs@openprivacy.org: "CVS update: openprivacy/htdocs"

    Date: Tuesday February 6, 19101 @ 18:53
    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

    -----------------------------------

    Update of /usr/local/cvs/public/openprivacy/htdocs
    In directory giga:/home/fen/projects/openprivacy/htdocs

    Modified Files:
            platform.shtml
    Log Message:
    added infrastructure and attack resistant sections

    *****************************************************************
    File: openprivacy/htdocs/platform.shtml

    CVSWEB Options: -------------------

    CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/platform.shtml?annotate=1.2

    CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/platform.shtml?rev=1.2&content-type=text/x-cvsweb-markup

    CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/platform.shtml.diff?r1=1.2&r2=1.1

    -----------------------------------

    Index: openprivacy/htdocs/platform.shtml
    diff -u openprivacy/htdocs/platform.shtml:1.1 openprivacy/htdocs/platform.shtml:1.2
    --- openprivacy/htdocs/platform.shtml:1.1 Tue Feb 6 13:03:22 2001
    +++ openprivacy/htdocs/platform.shtml Tue Feb 6 18:53:11 2001
    @@ -1,5 +1,6 @@
     <!--#include virtual="/includes/top.html"-->
     <!--#include virtual="/includes/navigation.html"-->
    +<!-- $Id: platform.shtml,v 1.2 2001/02/07 02:53:11 fen Exp $ -->
     
     <h3>Platform</h3>
     
    @@ -77,8 +78,37 @@
           explicitly permitting some uses and denying others
     </ul>
     
    +<h4>Supporting Infrastructure</h4>
    +OpenPrivacy is a distributed peer-to-peer network. As all communications
    +are anonymized and may be encrypted, it is highly censorship resistant,
    +though this can be enhanced further by using techniques currently being
    +implemented by these and other projects:
    +<ul>
    + <li>Freenet
    + <li>Free Haven
    + <li>Mojo Nation
    + <li>Freedom (ZeroKnowledge)
    +</ul>
    +
    +<h4>Attack Resistant</h4>
    +<ul>
    + <li>Denial of Service (DOS): left to the supporting infrastructure
    + <li>spoofing: impossible unless secret key is compromised
    + <li>replay: identical (duplicate) data is GC'd
    + <li>flooding: similar claims can be coalesced
    + <li>/shills/slander/false claims:
    + <ul>
    + <li>making unsubstantiated comments can damage the issuer's reputation
    + <li>anonymous (made with little or no backing reputation) shills/floods
    + are likely to be ignored
    + </ul>
    +</ul>
    +
     <h4>Standards based</h4>
    -OpenPrivacy builds on standards being used throughout the Internet, including
    +OpenPrivacy defines a few basic interfaces and leave implementation up to
    +the developers of the various services. However, our reference
    +implementation - and recommendation - is built on Internet standards,
    +including:
     <ul>
       <li>XML - all communications and objects are represented in XML
       <li>XMLDsig - the XML Digital Signature standard is used as the base of

    This archive was generated by hypermail 2b30 : Tue Feb 06 2001 - 18:53:11 PST