[Gzz-commits] gzz/Documentation/misc/hemppah-progradu mastert...

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Hermanni Hyytiälä <address@hidden>      03/03/03 06:55:34

Modified files:
        Documentation/misc/hemppah-progradu: masterthesis.tex 
                                             progradu.bib 

Log message:
        Anonymity

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/misc/hemppah-progradu/masterthesis.tex.diff?tr1=1.103&tr2=1.104&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/misc/hemppah-progradu/progradu.bib.diff?tr1=1.90&tr2=1.91&r1=text&r2=text

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/masterthesis.tex
diff -u gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.103 
gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.104
--- gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.103      Mon Mar 
 3 05:49:55 2003
+++ gzz/Documentation/misc/hemppah-progradu/masterthesis.tex    Mon Mar  3 
06:55:33 2003
@@ -1079,8 +1079,42 @@
 
 
 \subsection{Anonymity}
-Anonymoys \cite{352607}
-Anonymoys \cite{293447}
+
+According to \cite{dingledine00free}, there exists several kinds of anonymity. 
Author-anonymity is form
+of anonymity in which no one can link author to a specific document. In 
publisher-anonymity system,
+no one is able to link publisher to a specific document. Reader-anonymity 
means that a specific
+document cannot be linked to document's readers. This form of anonymity 
protects the privacy of a
+system's users. Furthermore, in peer-anonymity means that no peer can be 
linked to a specific document, i.e.
+no one is able to determine the peer, where document was originally published. 
Document-anonymity
+means that peer doesn't know which data it is currently hosting. Finally, 
query-anonymity refers is form
+of document-anonymity; when other peers performs data lookups, peer doesn't 
know which data it servers
+to the data lookup originators. As the authors cite, some of forms of 
anonymity may imply each other and
+possible issues are one area of future work.
+
+With regard to anonymity in Peer-to-Peer systems, there has been done much 
research work both at network 
+level layer \cite{tarzan:ccs9} and at application level layer 
\cite{reiter98crowds}, \cite{mixminionurl}.
+Research on anonymity outside of Peer-to-Peer context have been done also 
\cite{352607}, \cite{293447}.
+
+Obviously, providing several types of anonymity, anonymity often conflicts 
with other key properties of
+Peer-to-Peer system. Let's consider anonymity and efficient data lookup. In 
efficient lookup, we must know
+the peers responsible to given data in Peer-to-Peer system. Of course, when we 
know the peers responsible
+for the data, the anonymity of peer is lost. Fortunately, there are partial 
solutions to previously
+mentioned situations, i.e. pseudonym which is a partial form of anonymity. For 
instance, pseudonym can used for 
+addressing peer-anonymity by providing anonymous-like identifiers to peers 
(e.g., tightly structured peer 
+identifiers).
+
+Anonymity is widely used in those Peer-to-Peer system in which data 
publication is performed. These include
+Freenet \cite{clarke00freenet}, Publius \cite{pub00}, Free haven 
\cite{dingledine00free}, Crowds \cite{reiter98crowds},
+Tangler \cite{502002} and upcoming Mnet \cite{mneturl}. Forwarding proxies are 
used in Freenet, Crowds and 
+Free Haven in order to provide various types of anonymity. Tangler and Publius 
uses cryptographic
+sharing methods to split a data into data fragments \cite{Shamir1979a}. 
Mixmailer networks, such as
+\cite{mixminionurl}, are commonly used in distributed systems, which are able 
to provide level
+of anonymity
+
+Even if many existing Peer-to-Peer systems are able to provide some of the 
types of anonymity, there is no
+such a system which is able to provide all kinds of anonymity as listed above. 
Furthermore, the conflicts
+between anonymity and other Peer-to-Peer system properties requires more 
research work.
+
 
 \subsection{Access Control}
 \subsection{Fault-tolerance}
@@ -1089,19 +1123,12 @@
 \subsection{Other Security threds}
 
 
-\cite{daswani03openproblems}
-
-\cite{sit02securitycons}
 
 
 
-\cite{ajmani02conchord}
 
-\cite{reiter98crowds}
 
-\cite{tarzan:ccs9}
 
-\cite{pub00}
 
 \cite{grahamp2psecurity}
 
@@ -1295,6 +1322,10 @@
 
 
 \section{Summary}
+
+\cite{daswani03openproblems}
+
+\cite{sit02securitycons}
 
 Main problems in different approaches (own conclusions, based on research 
efforts):
 1) Decentralized, but structured
Index: gzz/Documentation/misc/hemppah-progradu/progradu.bib
diff -u gzz/Documentation/misc/hemppah-progradu/progradu.bib:1.90 
gzz/Documentation/misc/hemppah-progradu/progradu.bib:1.91
--- gzz/Documentation/misc/hemppah-progradu/progradu.bib:1.90   Mon Mar  3 
05:49:55 2003
+++ gzz/Documentation/misc/hemppah-progradu/progradu.bib        Mon Mar  3 
06:55:33 2003
@@ -1206,7 +1206,7 @@
 
 %Tangler publishing system
 @inproceedings{502002,
-       author = {Marc Waldman and David Mazi},
+       author = {Marc Waldman and David Mazières},
        title = {Tangler: a censorship-resistant publishing system based on 
document entanglements},
        booktitle = {Proceedings of the 8th ACM conference on Computer and 
Communications Security},
        year = {2001},
@@ -2043,3 +2043,20 @@
        key = {Mixminion},
        url ={http://www.mixminion.net/}
 }
+
address@hidden,
+       title = {MNet},
+       key = {MNet},
+       url = {http://mnet.sourceforge.net/}
+}
+
address@hidden,
+       author = {A. Shamir},
+       journal = {Communications of the ACM},
+       month = {November},     
+       number = {11},
+       pages = {612-613},
+       title = {{How to Share a Secret}},
+       volume = {22},
+       year = {1979}
+}