On Wednesday 12 May 2004 17:22, Shlomo Solomon wrote: SS> But that doesn't answer either of my questions: SS> 1 - why does it work at all if I didn't open a port in my firewall?
You only need an open port for incoming connections(i.e. sharing files). So you can still run it with some limited functionality <grin> It means that you are getting a so-called low-id. Thus you can only connect to non-firewalled clients. Of course, the downloads would not be as kickass, as you are limiting your sources list to something like 25% of the whole network. Ok, I see that I starting to just rephrase the original FAQ, so why don't you read it yourself? :)) http://www.overnet.com/documentation/faq.html http://www.overnet.com/documentation/lowid.html SS> 2 - does running Overnet pose a danger (with or without opening a firewall SS> port)? Well, look at it this way...overnet was still closed source, last time I checked(which is just now). Am not about to doubt the skill of the developers, but...my pet paranoia tells me that every server or client you are running poses a threat to security. It really does not matter if it has an open port or not as long as it is getting a data stream originating holy Random knows where. So locking it down into a chroot jail seems like a good idea, reducing the risk if done properly. In fact I admit that I done that when I was running overnet. It is statically compiled so locking it down is a matter of reading `man chroot`. -- Sincerely Yours, Vasiliev Michael ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
