Message boards :
Number crunching :
BOINC and Internet Access
Message board moderation
Author | Message |
---|---|
MikeSW17 Send message Joined: 3 Apr 99 Posts: 1603 Credit: 2,700,523 RAC: 0 |
I'm (now) only partially security savvy, so forgive me if this is a stupid question.... I run Zone Alarm firewall, I have no problem allowing boinc_gui.exe to access the internet - I'd get no work otherwise. But, every time I fire BOINC up. it also asks "Do you want to allow boinc_gui to act as a server?" .... Well do I? It tells me that it will listen on port 31416 - It seems not to make much difference if I say yes or no. I hate not really - inherently - understanding internet/TCP-IP/Windows security - but I hate even more that application readme/faq files never detail IP addresses/ports that the product can/might/should access ;-( [Jeez, I know I should know this stuff - I grew-up h**k**g the APRANET via DECSystem-10s etc for laughs way back when 8-)] <a><img border="0">[/url] |
CyberGoyle Send message Joined: 2 Jun 99 Posts: 160 Credit: 3,622,756 RAC: 26 |
Yes, allow BOINC to act as a server. BOINC needs to both send and receive (typical server activity) - send results and receive new work. Port 31416 is the RPC port BOINC communicates on. <a> |
jjhat1 Send message Joined: 24 Apr 03 Posts: 49 Credit: 61,357 RAC: 0 |
Well I think you really do not need it to act as a server. That feature is the GUI RPC that is for third party programs like BoincView. It probably would not hurt if you did allow it but you would not need to have it act as a server to send and receive work. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
|
EclipseHA Send message Joined: 28 Jul 99 Posts: 1018 Credit: 530,719 RAC: 0 |
> Yes, allow BOINC to act as a server. BOINC needs to both send and receive > (typical server activity) - send results and receive new work. Port 31416 is > the RPC port BOINC communicates on. > Nope.. Though it sends and rec's, that does not define a server. It's a client that contacts the server (services in the case of BOINC). Boinc does not contact the client. The request you are seeing is that the client listens for connections for things like boincview so that it can be controlled locally. It's funny that it seems to listen even if "-allow_remote_gui_rpc" isn't specified. This seems to be so that it can log an error message if an RPC connection is attempted without the command line parameter. |
wilsen Send message Joined: 15 Apr 00 Posts: 68 Credit: 73,527 RAC: 0 |
GUI RPC is activated by default for local access. That means every monitor program or alternative GUI can access the client, that runs at the same host. KEINE PANIK |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.