[cap-talk] Mapping multiple untrusted third party to a virtual TTP?

[David Barbour]

I've read a few articles related to this subject. The best is probably:

 Secure routing for structured peer-to-peer overlay networks
 http://www.cs.rice.edu/~dwallach/pub/osdi2002.pdf

which deals with untrustworthy nodes and concerns of 'conspiracies' - the
maximum percentage of such untrustworthy nodes that are cooperating.

Research focusing on Game Theory and Incentives is also interesting:

 http://cseweb.ucsd.edu/~vahdat/papers/infocom05.pdf
 http://p2pecon.berkeley.edu/pub/p243-EC04.pdf

How high 'm' can be raised really depends on:
* concerns for performance
* how easy it is to detect untrustworthy behavior
* the domain - for which behavior is trust required

But, in general, raising it above n/3 is really, really hard (Byzantine).

On Fri, Aug 14, 2009 at 3:24 AM, Rob Meijer <capibara at xs4all.nl> wrote:

> I was having an interesting discussion on TTPs a few days back that raised
> an interesting question about TTPs. I thought that with the high knowledge
> on this list with  related issues, someone here might be able to answer
> this question.
>
> The concept was that given that you :
>
> 1) Have a protocol that needs a TTP
> 2) Don't have a real TTP
> 3) Have some number 'n' of 'Untrusted' third parties.
> 4) Know that at most a number 'm' of these 'n' are in fact both
>   'Untrustworthy' AND 'Cooperating' and coordinating with the
>   untrustworthy peer.
>
>
> Would there from this be any way to implement a 'virtual' TTP from the
> combination of n untrusted third parties, and if so how low would 'm' need
> to be for any given value of 'n' ?
>
> Rob
>
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk
>



-- 
hubris and humility compose
perfectionism, paralysis, a curse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.eros-os.org/pipermail/cap-talk/attachments/20090903/ea3fb92f/attachment-0001.html