• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

v3.03 winnt CLi no longer linked at S@H ,any TA links for it? + a retired linux-gnu client comes back in v3.08

Assimilator1

Assimilator1

Elite Member
I was just browsing the SETI CLi download page to see if v3.03 winnt is still there ,unsurprisingly it isn't.
Do we have any TA sites that are hosting it (I'm sure someone said they had but I forget who!😱) ,let us all know again so that future members can stick with the faster client🙂.Also I'll add the link to my site.

The other thing I noticed whilst browsing the 'Client replacement' list is this

i686-pc-linux-gnu v3.08 restored from retirement 2003-04-07
v1.03 retired 2000-10-25

AFAIK this list hadn't been updated since about the time v3.03 was enforced!.
That client any use to anyone?
 
I was installing on a new machine last night and I couldn't get the 3.03 either... that's brutal... had to grab it from another PC and move it across the network.. Strange indeed. I'm gonna have to remember to keep the client on a CD or something just incase.
 
Seti@home
Information leakage and remotely exploitable buffer overflow in various seti@home clients and the main server.
Affected versions

Confirmed information leaking:
This issue affects all clients.

Confirmed remote exploitable:
setiathome-3.03.i386-pc-linux-gnu-gnulibc2.1
setiathome-3.03.i686-pc-linux-gnu-gnulibc2.1
setiathome-3.03.i386-pc-linux-gnulibc1-static
setiathome-3.03.i686-pc-linux-gnulibc1-static
setiathome-3.03.i386-winnt-cmdline.exe
i386-unknown-freebsd2.2.8 (Special thanks to Niels Heinen)
SETI@home.exe (v3.07 Screensaver)

Confirmed DoS-able using buffer overflow:
The main seti@home server at shserver2.ssl.berkeley.edu

Presumed vulnerable to buffer overflow:
All other clients.

Stop using earlier clients!
 
Once they recompile the newer clients so there's not so much of a huge speed loss, then maybe I'll change.

For now, the worst that can happen is i'll have to reinstall Windows, big deal
rolleye.gif



Confused
 
Originally posted by: n0cmonkey
Isn't that the version with the security hole?
Click to expand...

Yeah ,but no-one has actually been compromised this way ,personally speaking ,if your running SETIQ I can't see how it could be done.
 
Originally posted by: Assimilator1
Originally posted by: n0cmonkey
Isn't that the version with the security hole?
Click to expand...

Yeah ,but no-one has actually been compromised this way ,personally speaking ,if your running SETIQ I can't see how it could be done.
Click to expand...

If you are behind a NAT device you *should* be fine, but I'm paranoid and don't like the risk. I've worked too hard to have one of my machines compromised for a few minutes of faster WU crunching.
 
Originally posted by: Confused
Once they recompile the newer clients so there's not so much of a huge speed loss, then maybe I'll change.

For now, the worst that can happen is i'll have to reinstall Windows, big deal
rolleye.gif



Confused
Click to expand...

The worst that can happen is someone from the government shows up at your door and you don't see your computer again.
 
Originally posted by: n0cmonkey
Originally posted by: Confused
Once they recompile the newer clients so there's not so much of a huge speed loss, then maybe I'll change.

For now, the worst that can happen is i'll have to reinstall Windows, big deal
rolleye.gif



Confused
Click to expand...

The worst that can happen is someone from the government shows up at your door and you don't see your computer again.
Click to expand...
Why would the goverment take your computer because you're not running the latest S@H client?



As for the client download, you can just replace the 3.08 with 3.03 in the download address to get it.
ftp://alien.ssl.berkeley.edu/pub/setiathome-3.03.i386-winnt-cmdline.exe

 
Originally posted by: Spacehead
Originally posted by: n0cmonkey
Originally posted by: Confused
Once they recompile the newer clients so there's not so much of a huge speed loss, then maybe I'll change.

For now, the worst that can happen is i'll have to reinstall Windows, big deal
rolleye.gif



Confused
Click to expand...

The worst that can happen is someone from the government shows up at your door and you don't see your computer again.
Click to expand...
Why would the goverment take your computer because you're not running the latest S@H client?



As for the client download, you can just replace the 3.08 with 3.03 in the download address to get it.
ftp://alien.ssl.berkeley.edu/pub/setiathome-3.03.i386-winnt-cmdline.exe
Click to expand...

Because your computer has suddenly become part of a Chinese botnet and is helping to DDoS whitehouse.gov
 
Remember, in order to hack the old client, the hacker must redirect the address of the SETI server or proxy being used. So in my case for the Wildnet, the hacker would have to hack http://seti.tacube.com:5517, hack into the Wildnet (the only permanently connected computers), discover you can't do much of anything on that ramdisk except ssh, and ssh out somewhere else. All that and hope that the node didn't go down while they were at it (which happens quite frequently.)

Not worth it for me. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top