« Home | I just found my new cell phone. I have put off bu... » | 288th! Woohoo! » | More exploits and fun. DePaul university has not ... » | Well, gotta love the errors of others. Bugtraq wa... » | Controlling the users on a BSD box just became so ... » | I, for one, am quite happy that Brunching Shuttlec... » | OpenSOB (9:14 PM):I am lonely!GooglyMinotaur (9:14... » | I hate the Ann Arbor Art Fair. The fair has yet t... » | Throw 40 machines at a project, reap the results: ... » | D'oh! I forgot that distributed.net usually has a... »

241st! Ya know, I am not sure why my RC5 output is increasing so much lately. I actually disabled the client on my main server at home. The server is stuck between two dressers and has a second server sitting on top of it. Needless to say, the air flow isn't so great and the temperature was simply too hot when running the proc at 100% 24/7. Maybe someone else is cracking for me... That would make for a pretty cool trojan/virus. Have it simply install dnetc then attempt to infect other computers. When it was finally discovered, distributed.net would be shut down, but hopefully not until I had won the $1000 prize.