On Fri, Nov 11, 2005 at 11:00:26AM +0000, loki tiwaz wrote: > by adding a protocol to signify persisting connections (so that while a What about clients maliciously manipulating the protocol to pretend that a service has been rendered? > circuit operates it is recognised as such) and a single signature check at How do you reliably prove that a service has been rendered? > the beginning of the circuit establishment. sure it will add *some* load to > the server's cpu but the verification only has to be done once every 15 > minutes per user at the most. I'm not worried about extra load. I'm not sure how to build an attack-resistant protocol, without a finite amount of tamperproof coins circulating in the network. -- Eugen* Leitl <a href="http://leitl.org";>leitl</a> ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.leitl.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE
Attachment:
signature.asc
Description: Digital signature