posted on Sep, 20 2004 @ 12:59 AM
There were reports today that the SETI@Home main website had been compromised, but this may be an inaccurate assessment. The SETI staff say now that
the problem was merely an error on the web server.
September 19, 2004
Early this morning campus got a call from SANS that the seti@home classic web site appeared to be hijacked. At that point campus (rightly so) blocked
access to our site at the campus router. As it turns out though, we were not hijacked at all. Our nightly front page regen script had malfunctioned
and produced a truncated page. This is now fixed. Please visit the link provided for the complete story.
The SANS report is archived on the Internet Storm Center
SETI@Home site problems
Very early this morning we received a report that the SETI@Home site had been changed for some odd reason. In addition, there was an unexplained
server crash on the 13th. These things combined lead to a very disconcerting situation.
Our concern at ISC is a _possible_ compromised SETI client that would allow unauthorized access into the machine(s) on which it resides. As with any
software published for public consumption, it is always a good idea to have MD5 sums or PGP to go along with it. We are _strongly_ encouraging all
users who have downloaded the client to double check that what they have downloaded is the correct version and date/time stamp. Please visit the link provided for the complete story.
It would not hurt to check, but I am not sweating this situation. The machines on which I run S@h, both versions, check out OK and are not
registering any unusual traffic or other activity.