[RC5] RE: Do not forget about the cheaters :)

Décio Luiz Gazzoni Filho decio at revistapcs.com.br
Thu Jan 8 09:03:24 EST 2004

Hash: SHA1

Identity-based checking is far from ideal. This is the kind of thing that 
easily gets hacked. If there's a way to mathematically prove, up to a certain 
level of confidence, that the work was actually done, I don't see why one 
would do differently.


On Thursday 08 January 2004 11:24, groovyr at comcast.net wrote:
> >I suggested something like this to Bovine in an email  Tue 18/07/2000
> >12:03.
> >Slightly more succinct than the Stanford paper IMHO :-)
> >(Clearly it doesn't cvoer quite as much ground.)
> yes that should work well.    So I  have to ask what was
> Bovine's response?
> i still say ALL blocks should be traceable to the client.
> Hacking the identity of the client would not work since
> the proxy servers could assign a new marker on each flush
> based on Ethernet MAC address and IP and as well as info
> added only the server side knows making it nearly impossible
> to hack a new identity.
> If no match then the server would not accept that flush.
> This would stop the cheater who is running many clients
> from one box and using many users names.  to stay hidden
> and under the radar.
> _______________________________________________
> rc5 mailing list
> rc5 at lists.distributed.net
> http://lists.distributed.net/mailman/listinfo/rc5
Version: GnuPG v1.2.3 (GNU/Linux)


More information about the rc5 mailing list