Re: exit policy

2008-02-18 Thread Andrew
NavouWiki schrieb: I would like to set an exit policy, but at the same time, I would like to be safe. I want my cake and eat it too. Is there a suggested safe exit policy? As far as websites go, what is preferred is the ability to read websites, but not write, such as would be done on

Re: iptables and tor

2008-02-18 Thread Michel Arboi
On Feb 10, 2008 1:07 AM, dante [EMAIL PROTECTED] wrote: Hi everyone, Has anyone given any thought as to what firewall rules to use on a linux system running a tor server? Assuming that your tor daemon runs under a dedicated UID or GID (e.g. tor), you can use iptables -m owner --uid-owner

Re: exit policy

2008-02-18 Thread Dominik Schaefer
Andrew schrieb: NavouWiki schrieb: As for end-to-end encryption, you could allow exit only to ports that are commonly used by encrypted protocols (like 443 for https, 465 for SMTPS, 993 for IMAPS... browse wikipedia to continue that list to your satisfaction). I just want to add: The

Re: max number of file descriptors hard coded

2008-02-18 Thread Nick Mathewson
On Sun, Feb 17, 2008 at 06:36:13PM +0100, Olaf Selke wrote: Narf! debugging the [warn] Error creating network socket: Too many open files messages I just found the max number of file descriptors apparently being hard coded in or.h to a value of 15.000. Raising the number using ulimit -n