sorry, just reread your email, and your reference to open networks... yes you are probably right. On Oct 31, 2009, at 1:24 PM, Daniel Trueman wrote:
PLOrk virtually always works on a closed LAN, not connected to the outside world.
dt
On Oct 31, 2009, at 1:22 PM, Kassen wrote:
Dan;
"Allow all incoming connections," which shouldn't be a security issue if you are running a LAN, and probably not much to worry about regardless (mine are all always set that way).
I really wouldn't do that on a open network. Of course the chances of you personally being targeted by something malicious are quite low but the consequences could be devastating, think not just of what could be downloaded (creditcard numbers, etc) but also of the kind of thing that could be planted on your computer. A thing like that could easily devastate your life, even if you could demonstrate you were unaware of it. I'd instead white-list all relevant peers like -say- all of plork. That should significantly reduce the risks while preserving most of the convenience.
Back on topic; David, these stuck computers, does Chuck take excessive amounts of cpu on them while they are stuck? If relatively little cpu is used it's probably stuck waiting for some event, if a lot is used it'll be something else.
Yours, Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users