Re: TransPort, DNSPort, and pf

[Scott Bennett <bennett@xxxxxxxxxx>]

     On Fri, 31 Dec 2010 03:49:24 -0500 Roger Dingledine <arma@xxxxxxx> wrote:
>On Fri, Dec 31, 2010 at 12:53:10AM -0600, Scott Bennett wrote:
>> hellas# su _tor
>> $ tor --verify-config
>> Dec 30 23:33:41.799 [notice] Tor v0.2.2.17-alpha (git-dadd9608d2720368). This is experimental software. Do not rely on it for strong anonymity. (Running on FreeBSD i386)
>> Dec 30 23:33:41.817 [warn] open("/dev/pf") failed: Permission denied
>> Dec 30 23:33:41.818 [warn] Failed to parse/validate config: Unable to open /dev/pf for transparent proxy.
>> Dec 30 23:33:41.818 [err] Reading config failed--see warnings above.
>> 
>>      My first question is, why does tor want to open /dev/pf when all packets
>> from the internal network are redirected to tor on the loopback interface
>> anyway?
>
>Because Tor still needs to be able to learn where the original destination
>was. Looks like it asks your OS that question through /dev/pf.
>
>See connection_ap_get_original_destination() in src/or/connection_edge.c

     Okay.  I'll take a look at that.
>
>>  To get tor to stop complaining, I had to change the group of /dev/pf
>> from wheel to _tor and change the device's permissions from 600 to 660.
>
>Hm. I'm going you're on net or free bsd?

     FreeBSD 7-STABLE.
>
>Quoting from get_pf_socket():
>#ifdef OPENBSD
>  /* only works on OpenBSD */
>  pf = open("/dev/pf", O_RDONLY);
>#else
>  /* works on NetBSD and FreeBSD */
>  pf = open("/dev/pf", O_RDWR);
>#endif
>
>No idea why it would need read-write in particular on /dev/pf, but who
>am I to answer the mysteries of BSD.
>
>In any case, Tor expects you to start Tor as root if you want the pf
>support to work, so it can open your /dev/pf correctly. That means you
>should use the 'user' torrc option and Tor would drop privs once it's set
>things up. (See the call to get_pf_socket() in options_act_reversible().)

     It was already running.  I made the changes to torrc and gave tor a
SIGHUP.  The changes to /dev/pf are not permanent (so far) because I made the
changes by hand and haven't yet changed /etc/devfs.conf.
>
>>  It
>> seems to me that neither should be necessary and that tor should not access
>> /dev/pf.
>
>Do you know another way to do transparent proxying on BSD? I confess
>that Linux's way (a getsockopt call) does look simpler. :)
>
     I've never delved into this at all.  I guess I'll just leave it as is
and let tor's startup phase as root handle it in the future.  What does LINUX's
getsockopt() return that FreeBSD's doesn't?


                                  Scott Bennett, Comm. ASMELG, CFIAG
**********************************************************************
* Internet:       bennett at cs.niu.edu                              *
*--------------------------------------------------------------------*
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."                                               *
*    -- Gov. John Hancock, New York Journal, 28 January 1790         *
**********************************************************************