[rc5] Suggestion for protocol

Michael Graff explorer at flame.org
Mon Jun 23 17:37:08 EDT 1997


Honza Pazdziora <adelton at informatics.muni.cz> writes:

> This would prevent people from downloading blocks and reporting them
> back as negetive without ever looking at them.

There is another tactic as well:  Have the key server send out known
good keys from time to time and see if they are reported as bad or
not.

If
	(1) the blocks sent out are more random than they are now, and
	(2) the client doesn't brag when it finds a good key,

this would work.

The other possibility would be to embed an encryption key within the
client itself, and have it use that as authentication.  That really
sucks, but it would work.

Of course, you could also require that the PERSON running the
client register themselves and get a special secret key.  When
returning blocks to the server the key would be used.  If one
specific key started sending in bad results (tested by sending it
known good blocks from time to time) it could be silently ignored
from then on.  Don't drop the client, just send it already computed
blocks and let the spammer think they're getting away with something.

--Michael
----
To unsubscribe, send email to majordomo at llamas.net with 'unsubscribe rc5' in the body.



More information about the rc5 mailing list