[RC5] Who cracked that block ??

gindrup at okway.okstate.edu gindrup at okway.okstate.edu
Tue Jul 7 18:34:10 EDT 1998

     When a client cracks a block, the client imprints the "completion 
     record" with the e-Mail address that the client is using.  This 
     couplet, (completion record, e-Mail address), is sent (essentially) 
     unaltered through the (personal) proxy network back to the master 
     keyserver where the e-Mail address part is used to determine who 
     gets the blocks.
     If you don't give a fully qualified e-Mail address, then the 
     keyserver can't associate the completion record with you.  I believe 
     that there are two large "bins" at D.Net.  The first bin contains 
     those blocks completed by clients which have never had the default 
     changed -- i.e., they are credited to D.Net.  The second bin is 
     "malformed addresses" -- i.e., they are credited to no one.
     The official D.Net line for a long time is that it would be too much 
     manual processing to handle reassigning previously returned blocks.  
     This is (one of) the reason(s) that blocks don't follow you as you 
     go from team to team.
     There used to be an option for pproxies to alter the e-Mail address 
     of the couplets that passed through them.  I recall that there were 
     a couple of abuses -- where pproxies were set up for public use but 
     were reassigning all the blocks to the pproxy owner's account.  This 
     option was removed so that such abuses could not occur.  The 
     original idea was to do what you suggested, but that method was 
     abused.  Imagine if two or three people were cracking blocks in your 
     company through your pproxy and then suddenly noticed that they were 
     never creditted for the blocks...
     Finally, as a source of "future-proofing", it is a good idea to have 
     a fully qualified e-Mail address in the client configuration.  If 
     one of those machines was ever migrated to a direct Internet feed, 
     it would be able to crack for you without your intervention (to 
     repair the e-Mail configuration item).
            -- Eric Gindrup ! gindrup at okway.okstate.edu

______________________________ Reply Separator _________________________________
Subject: RE: [RC5] Who cracked that block ?? 
Author:  <rc5 at lists.distributed.net> at SMTP
Date:    7/6/98 9:38 PM

Ok, here I go again, mis-understanding things. I set up several computers all 
using wingui clients. Then I set up a server using a pproxy. In order to be 
able view the keyrate graph and all, and also to see the various email 
messages. My concept was that only the pproxy got my email address. Each 
client got the local network email address. (No dot com or anything. ) So my 
scanning workstation name is 'scanner' , it had 'scanner' as it's email 
address, because that is the machine that the blocks were cracked on (when I 
send email to that machine, I address it as scanner, I address my self on the 
local net as bmeyer, not bmeyer at rocsoft.net.) So what you're telling me, is 
that all those blocks on all those different machines are not being credited 
to my email address? (The pproxy email address?) This would mean that every 
machine needs to have my email address in the setup, or I don't get credit 
for it. In this case, someone is getting a lot of free, unclaimed blocks. 
(Where do these mystery blocks go anyway? I lost a full days worth of about 
600 blocks a week or two ago due to a screw up on my config file)
        Bruce D. Meyer
-----Original Message-----
From:        owner-rc5 at lists.distributed.net 
[mailto:owner-rc5 at lists.distributed.net] On Behalf Of Ryan Schmidt 
Sent:        Friday, July 03, 1998 6:28 PM
To:        rc5 at lists.distributed.net
Subject:        Re: [RC5] Who cracked that block ??
>If it is the latter, remember that you can now submit blocks via email. 
>This can be really handy unless you have different users logging 
>in(which would mean different email addresses).  Maybe you could email 
>theseblocks to an account you have at home which you could then forward 
>under YOUR email address to the d.net.
Remember that it doesn't matter what e-mail address you send your bocks 
They'll get credited to the e-mail address you have set up in your client's 
>At what stage, exactly, does the cracker's address get associated with a 
>block ?
Right when it's cracked. The e-mail address in your client's .ini file is 
encoded into each completed block. This enables multiple clients with 
e-mail addresses to use the same buff-out files and still be properly 
And it lets you e-mail buff-out files from a different address than the one 
actually cracked the blocks.
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net 
rc5-digest subscribers replace rc5 with rc5-digest
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net 
rc5-digest subscribers replace rc5 with rc5-digest

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

More information about the rc5 mailing list