1042 |
|
|
1043 |
Traditional overload of targeted peers is best known form of distrubuted Denial of Service attack (DDoS). For example, |
Traditional overload of targeted peers is best known form of distrubuted Denial of Service attack (DDoS). For example, |
1044 |
hostile entity can attempt to burden targetted peers with garbage packets. As a implication, peers may act |
hostile entity can attempt to burden targetted peers with garbage packets. As a implication, peers may act |
1045 |
incorrectly or stop working. DDoS attack may be very severe, especially if rate of replication in Peer-to-Peer system |
incorrectly or stop working. DDoS attack may be very severe, especially if rate of replication and caching |
1046 |
is low. This may lead to data loss in the Peer-to-Peer system. Daswani et al \cite{daswani02queryflooddos} has done |
in Peer-to-Peer system is low. This may lead to data loss in the Peer-to-Peer system. Daswani et al |
1047 |
research regarding to this subject. Authors suggest efficient load balancing policies for Peer-to-Peer system in |
\cite{daswani02queryflooddos} has done research regarding to this subject. Authors suggest efficient load balancing |
1048 |
order to prevent massive system failures. Sit et al \cite{sit02securitycons} suggests that identifier assignment |
policies for Peer-to-Peer system in order to prevent massive system failures. Sit et al \cite{sit02securitycons} |
1049 |
algorithm for peers would assign identifier with respect to network topology and replicas should be located |
suggests that identifier assignment algorithm for peers would assign identifier with respect to network topology |
1050 |
physically to different locations. |
and replicas should be located physically to different locations. |
1051 |
|
|
1052 |
\subsection{Data authenticity and integrity} |
\subsection{Trust, data authenticity and integrity} |
1053 |
|
|
1054 |
|
Quite recently, widely used Public Key Infrastructure (PKI) has been deployed in distributed |
1055 |
-Could we use SDSI/SPKI in our system (it's hierarchical), like in ConChord \cite{ajmani02conchord} |
systems \cite{rivest96sdsi}, \cite{spkiworkinggroup}. PKI is an reliable technology for securing |
1056 |
-is there any other implementations of SDSI/SPKI-like systems ? |
data in rather \emph{static} computing systems, such as in the Internet. However, in Peer-to-Peer |
1057 |
-SDSI/SPKI is not optimal for us, but somewhat working solution |
network, the problem of PKI-based security mechanism is the maintenance of the keys as participating |
1058 |
-in our model: trust = trust no one |
peer constantly join and leave the system. Specifically, the distribution of key changes comes an essential |
1059 |
-give a brief explanation of current techiques in accountability and trust |
problem in ad hoc enviroments. These include revokation of keys and new key distribution. Also, the scenario |
1060 |
|
in which hostile peers are present has to be addressed. |
1061 |
|
|
1062 |
|
ConChord \cite{ajmani02conchord} is the first Peer-to-Peer system which has a support for PKI based |
1063 |
|
security infrastructure. Unfortunately, ConChord is in early in development and lacks of important |
1064 |
|
features of PKI to be fully usable yet. Furthermore, the hierarchy of SDSI/SPKI may a problem for |
1065 |
|
Peer-to-Peer systems, in which hierarchy is intentionally missing. |
1066 |
|
|
1067 |
|
|
1068 |
\subsection{Anonymity} |
\subsection{Anonymity} |