It assumes global visibility, and unspoofability: Every node must know
the entire network, and it must not be possible for a node to lie about
its peers. The latter is something we need to address for premix
routing. As for the former, we will need *local* visibility for premix
routing - we need to be able to see every node in a few hops, and
determine with a reasonable confidence whether their existence is
plausible - but global visibility would be expensive, and would help
attackers.

On Wed, Aug 23, 2006 at 06:50:41PM -0700, Yongqian Li wrote:
> I have a idea about insertion verification. I am not
> sure whether it will work or not but here goes:
> 
> Whenever a node receives a insertion, it will pass it
> on and sign it. It then passes back the signatures of
> its peers down the chain as well as it own signature.
> For example:
> 
> A->B->C->D
> 
> D will give to C its signature and C will give B the
> signature of D as well as it's own and so on. A will
> receive the signatures of B, C, and D. Of course, B
> can fake those identities. To prevent that, A trusts
> the validity of those signatures porportional to their
> rep. If the rep of C and D are high, then B probably
> did insert those files. If the rep of C and D were low
> though, B probably faked those identities. 
> 
> Would this work? What do you guys think?
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
> 

-- 
Matthew J Toseland - toad at amphibian.dyndns.org
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20060825/ca06aa30/attachment.pgp>

Reply via email to