[Dshield] vunerability windows

Rich Weissler Rich.Weissler at mail.wvu.edu
Tue Feb 10 14:48:57 GMT 2004


Yes, the user loads client software on their system, so it is only the
user computer which makes the outbound connection.  A more complete
answer from their FAQ:

-----<snip from: http://setiathome2.ssl.berkeley.edu/faq.html#q1.11
>------------

Does SETI at home work through firewalls (or proxies)? 
SETI at home uses the HTTP protocol, and work through any semi-transparent
firewall that allows outgoing Web traffic. The latest versions of
SETI at home should work through more restrictive firewalls and proxies. 

If you are having problems connecting from Windows through a SOCKS
proxy, you could also look into SocksCap by NEC at
http://www.socks.nec.com/sockscap.html and Hummingbird Socks at
http://www.hummingbird.com/products/nc/socks/index.html Both let you
use software as if it were "directly connected to the Internet". 

If you're STILL having trouble connecting through an HTTP proxy server
and you are running SETI at home on an older version of Windows 95,
Microsoft has an updated Winsock 2 driver which corrects the problem,
and lets the SETI at home client connect. Search for "Windows Socket 2" in
the Product Information section of the Microsoft web site. The file is
about 986 kbytes, and post-dates Windows 95 Service Pack 1. 
---------------------<end>-----------------------------

>>> allan.malig at equitablepcib.com 2/9/2004 8:15:36 PM >>>
Interesting.   BTW, is it true that SETI has a project before that uses

the CPU resources of an online computer (with permission  of course)
when 
it's on screen saver mode?  If ever this is true, wonder how do you set
it 
to pass through  a firewall :-) 

Regards


Andy Streule <andy.streule at lythamhigh.lancs.sch.uk>
Sent by: list-bounces at dshield.org 
02/09/2004 06:32 PM
Please respond to General DShield Discussion List

 




More information about the list mailing list