No announcement yet.
SETI as a Service
Collapse
X
-
I hope you are not planning to 'borg' computers without the owner's permission :no:
nothing wrong with healthy competition, just don't want to see anyone taking it too far.
*btw, what did you put in your autorun.inf?
I made one for installing OpenOffice from CD, I'm just curious for comparison
[autorun]
open=setup.exe
icon=icon.ico
Comment
-
Originally posted by minibubbaI hope you are not planning to 'borg' computers without the owner's permission :no:
nothing wrong with healthy competition, just don't want to see anyone taking it too far.
Thats why I have a disclaimer....
Comment
-
Originally posted by minibubbaI hope you are not planning to 'borg' computers without the owner's permission :no: nothing wrong with healthy competition, just don't want to see anyone taking it too far.
I guess it wouldn't have anything to do with this quote would it?
Kane2G I will go and borg as many systems as I need to to be ahead of Cheez.
Comment
-
Originally posted by minibubbaI hope you are not planning to 'borg' computers without the owner's permission :no:
nothing wrong with healthy competition, just don't want to see anyone taking it too far.
*btw, what did you put in your autorun.inf?
I made one for installing OpenOffice from CD, I'm just curious for comparison
borg.bat
Comment
-
November 14, 2003
Over the past few weeks we've been getting reports from users who found unauthorized installations of SETI@home on their systems. It should be made clear that this is not due to a security flaw in SETI@home itself, but a flaw in your system that allows viruses to infiltrate and install our software.
In one case, a user found a Windows command line client running under the name "cpuidle" in the directory:
D:\WINDOWS\system32\drivers\etc\CPUIDLE
There is a real program out there called "cpuidle" - this particular infection was running SETI@home under this same name to confuse the user into thinking it was the valid "cpuidle" and not a fake one.
Another user claimed that they got infected this way over an IRC channel.
In the past, known worms were distributed around the internet that infected systems, causing them to download SETI@home and execute it. For example, we already know about this one from back in 2001:
http://[email protected]
Unfortunately, at this time we don't know much about the worm/virus which may be doing this. If you have any clues, please pass them along to us. We'll update this web page as we gather more information.
Comment
Comment