[RC5] client protocol security

David McNett nugget at slacker.com
Wed Nov 19 14:11:55 EST 1997


>Are blocks tagged via IP, email address, or some other identifier in
>the database logs?  It would make it really easy to invalidate all
>blocks returned by a weasel, or even by a client which is discovered 
>to be buggy after-the-fact.  Or is this in the v3 protocol?  ;-)

The logs tell us the timestamp, block ID, block length, email address,
submitting IP, keyserver used, cpu, os, and client version.

-/\/ugget
 ________________________________________________________________________
|David McNett      |To ensure privacy and data integrity this message has|
|nugget at slacker.com|been encrypted using dual rounds of ROT-13 encryption|
|Birmingham, AL USA|Please encrypt all important correspondence with PGP!|

--
To unsubcribe, send 'unsubscribe rc5' to majordomo at llamas.net
rc5-digest subscribers replace rc5 with rc5-digest



More information about the rc5 mailing list