S@H Poll - Whose still running v3.03 & who has switched to v3.08?

[Assimilator1]

I'm just curious really.

For those running v3.03 (most of us I hope😉) there is a very simple fix for the low risk security flaw in it.Look here for more info 🙂

If your wondering why those of us running v3.03 have not upgraded to v3.08 its because it is slower at average AR WUs (about 12%) which compromise the bulk of WUs

For those who want to switch back to the overall faster v3.03 CLi get it here from an official S@H site 🙂

 

[MoFunk]

3.03

 

[Smoke]

All Users of the TeAm Smokeball SetiQueue should still be running Version 3.03 because .......................................................................................................................................................................................................................................................................................................

I did the FIX. 😛 😀

 

[JWMiddleton]

3.03...I'll admin that I didn't even know about the new version. 12% slower....hmmmm.....Well, 3.0.3 is still working for me.

 

[panhead49]

i did not know there was a diffrence in speed ......im running 3.03 on my main machine and 3.08 on some of my other crunchers........that is my 1 vote ......i may switch now....😀

 

[ICXRa]

My part of the fleet is all still on 3.03

 

[Swanny]

3.03 for me.

 

[Spacehead]

Didn't vote because... i run both 🙂

I have v3.03 on my Win 98SE comp. I have a copy of both the v3.03 & v3.08 on my Win XP comp.
I screen my WU's that go to each computer. When i get a VLAR WU(currently 0.350 or less) i have the v3.08 client process it. The best of both worlds, as the v3.08 is faster than the v3.03 client on VLAR WU's.
I'm still looking for the cutoff point though, angle range wise, at which v3.08 is better than v3.03. It's less than 0.380:
0.380 AR
v3.03 - 3:39:37
v3.08 - 4:06:36

Currently v3.08 has completed 32 WU's at an average of 3:34:27 🙂

 

[CraigRT]

3.03 CLI

if i had to switch all my clients, i'd probably switch projects. 😛

 

[gistech1978]

3.03 cli
whats the FIX smokeball?

 

[Smoke]

Originally posted by: gistech1978 3.03 cli
whats the FIX smokeball?

Just click on the link in Assimilator1's lead-off post. It will take you to our SETI Offsite Forum and a thread about this topic. 😉

 

[gistech1978]

hmmm it might help to read a post instead of just looking @ the poll

thanks
😛

 

[deerslayer]

3.08 😱

 

[BofRA]

3.03 🙂

Too many clients to go replace!!!!

 

[Assimilator1]

Space head
Good point ,pitty we can't use SETIQ to auto redirect VLAR WUs to v3.08

link to v3.03 CLi added to 1st post

 

[Smoke]

Posted by OhioDude in the referenced thread:

Smoke --

On your system(s) that run SetiQueue, search for the "hosts" file using Windows Explorer. Edit it in a text editor (notepad is fine) and add a line at the end like this:

66.28.250.122 shserver2.ssl.berkeley.edu

(The IP and the server name are separated by a space or a tab character.)

If every one of your clients transmits to your setiqueue system, then that is the only one you need to worry about. In other words, any system that transmits directly to Berkeley should have the line above added to the hosts file.

The exploit requires a spoof entry to be added to the DNS cache on the system transmitting wu's to direct requests intended for Berkeley to a different system. TCP/IP always looks to the hosts file before looking at DNS to resolve host names so adding the line to your hosts file will always direct requests to Berkeley's IP regardless of what's in your DNS cache.

 

[Kelemvor]

I just started running S@H again so I got 3.08 with SetiHide because it was there. I swapped on 3.03 so we'll see what happens...

 

[xjamesx]

3.03 CLI

 

[networkman]

3.03 CLI

 

[WayneS]

Originally posted by: Assimilator1
Space head
Good point ,pitty we can't use SETIQ to auto redirect VLAR WUs to v3.08

Don't know if this is just fluke but I've been running 3.08 on one of my machines for about 2 weeks now and after a couple of days my SETIQ started sending all the VLAR WUs to that machine. None of the others have had a VLAR WUs sent to them in 10 or so days. It's sort of like when I was running mostly Windows95 with one NT box and SETIQ seemed to send most of the VLAR WUs to the NT box. Might not hold but it seems to be working well at the moment.

 

[SlowBones]

3.03 CLI at home, 3.03 GUI at work.

 

[Rattledagger]

Well, BOINC test_client said: Measured floating point speed -488.31 million ops/sec

v3.08.

 

[GhettoFob]

Originally posted by: ReaganCRW
3.03 🙂

Too many clients to go replace!!!!

 

[BobTheWizard]

3.03..... don't want any slowdowns......

 

[Assimilator1]

Good to see most people on v3.03🙂