RC5@Distributed.net is STILL getting blocks
Everyone that is cracking should check their PCs - email@example.com has been getting blocks for about two weeks now. Whoever has joined around/since that time should check to make sure they aren't giving their blocks to firstname.lastname@example.org, but instead are getting credit for them.
Life is Short. Crack Hard.
Oh, btw, yesterday was my one-year anniversary with distributed.net. Best day I've had in quite a while.
I got the By Host stats backup. So finding out whose clients' are cracking for email@example.com will be a lot easier. Except in this case.
This is the same person I posted a message about back on Aug 1st. They have been cracking for firstname.lastname@example.org since July 31st. They are new so I can't tell who it is. It also means I can't mail them to tell them the bad news.
Anyone who is on the *.wcom.net domain and uses a dialup. Please set you client to the right email address.
Has anyone else noticed that the client seems to make the out-buffer file coded to the e-mail address?
I recently changed e-mail addresses for the contest. I changed the e-mail out address on the machine that I was sending out the completed blocks. However, it continued to send the blocks to the old address, the address that the buffer was created from.
So, to finally get rid of the old address, I had to dump the buffers, make sure every client I had running had the new address, to prevent one of the network stations from getting there first with the new buffer, and delete the empty buffer out making sure a NEW buffer was made.
Anyway, I see that the freebie blocks to DNET are still happening and this may be why.
Well the blocks from *.wcom.net have stopped, but blocks coming from usrtc*-*.kiva.net and usr*-*.kiva.net have taken his place. It almost looks like it is the same guy, but he is moving his computer from place to place.
I sure wish he would check the stats and complain about not appearing. So we could get this over with.
Watching email@example.com is like getting kicked in the jimmy day after day.
If you want to know real pain, several months ago, after I had initialized a new system, I dumped 1,100 blocks to good ole' DNET because the client had made the buffer default to their address .
[This message has been edited by cwizard (edited 08-16-99).]
New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke