Probably bad news on the PHF!!!

[Tripleshot]

Orange Kid

My conspiracy idea isn't so far fetched after all.You think there is an alterier motive on behalf of Dnet tracking the PhF? hmmmmmm.

 

[DutchJake]

IF the PhF uses a trojan, how did he get it to level out so neet for the different accounts?

the computer use of home-users is unpredictable!
so how many to infect for let's say 25k:
400 Mhz does around 300 blocks per 24 hours, at about 6 hours a day
is 75 => 333 PC's per infected account! (correct me if I'm wrong)

he needs a lot less PC's if he controls them at a company because he let's them run 24/7

My guess is that there are a lot of copycats, Fake Phantom Flushers (FPhF ) I just hope the real one is helping me, and not some fake one, who uses a trojan...

DutchJake

 

[fraek]

The problems could be solved if it is possible for the users to login and see a list of the IP numbers which submitted blocks of the last day. Then a user can see which IP numbers are his and which aren't. By using checkboxes it could be possible to define which IP numbers you like to receive blocks from and from which you don't. If you like the blocks from the phantom flusher you keep the boxes checked.

 

[nulkelvin]

I don't think getting personal user information from someones computer is the right thing to do for a D.net client. I personally wouldn't like that.
That's why it's not a solution for the PhF problem.
Has anyone thought that it was maybee a trojan-infected-cdrom shipped with a magazine or something........

 

[RaySun2Be]

I haven't gotten any hate mail.

 

[vss1980]

I'm pretty sure there is a phantom flusher.

I'm also not going to doubt that there is a trojan or two out there trying to make some teams look bad. Dont forget, all the teams face a lot of competition and many are techie sites, with participants who know more than enough to write the odd trojan.

The only solution to the problem that I can see is if a personal password/encryption system is used that are submitted with the blocks.

 

[mindless]

I think the idea of a password os a good one, simply have the ini file with emaial and password which you would have emailed to you from dnet. But theres a problem with that, if I remember correctly, you cant get your password until after you start cracking, so something would have to change but good idea non the less.

But the idea of it poking around in the registry, or retrieving ANY information from MY machine is bullocks and the program would never cross my phone line.

 

[dkappos]

There is also another problem with the password... more serious. The ID is written in an .ini file so anybody who can read this file can easily do whatever he wants with your account. So what happens if you assimilate somebody else?s computers and he decides to retire the account to another one?

[edit] To solve this problem we would need the ID and the password to be different. It wouldn't be that difficult for DNET to give you those if there was a subscription. But it is the way it works now.[/edit]