Arm Release 1.4.0

[Hans Schnehl]

Answering to Fabian's mail, which came a minute before I was about send a
more verbose answer.


On Sun, Dec 05, 2010 at 01:02:16PM +0100, Fabian Keil wrote:
> Damian Johnson <atagar1 at gmail.com> wrote:
> 
> > Hi all. I've checked in the resolver fixes (thank Fabian and Hans!)
> > and a test tarball is available at:
> > 
> > http://www.atagar.com/transfer/tmp/arm_bsdTest.tar.bz2
> > http://www.atagar.com/transfer/tmp/arm_bsdTest.tar.bz2.asc
> 
> Thanks.
Thanks, too.  BTW where is the git repo, please ?   


> 
> > For BSD I'm using the following commands:
> > sockstat -4 | egrep '<process>\s*<pid>' | grep -v '*:*'
> > procstat -f 'pgrep <process>' | grep '<pid>' | grep -v '0.0.0.0:0'
> 
> Neither of those commands work for me. To let Arm figure out
> Tor's pid I still need the pgrep patch I mailed you yesterday.


It did work fine under FreeBSD 7.4-PRERELEASE with sockstat the way you
suggested. 
I modified in src/util/connections.py again to 
RUN_BSD_SOCKSTAT = "sockstat -4c | grep '%s%s' "
(See Fabian's patch.) This works fine, too. Just one cycle less.
Neither of the other options though did succeed in displaying a connection
list.



> 
> Attached are the patches I used to get it working on FreeBSD 9.0 CURRENT.
> I also rebased the sockstat+awk patch, but sockstat+grep probably works
> reliably enough.
> 
> One unrelated problem I noticed is that Arm tends to show local
> connections as Outbound. A connection from the Privoxy jail to
> the Tor jail:
> 
> _tor     tor        2750  25 tcp4   10.0.0.2:9050         10.0.0.1:20528
> 
> shows up as:
> 
> [public gateway IP address scrubbed]:9050  -->  <scrubbed>  0.0s (OUTBOUND)

Can verify this, running arm on a host connecting to a jail's tor controlport
results in this.

> 
> Given that the connection doesn't leave the system, replacing
> the Tor jail IP address with the public IP address of the gateway
> is a bit confusing.
> 
> Also, when running Arm outside the Tor jail, the Tor
> configuration file isn't found.


An old torrc located in the  host in the same path as the jail,  I
wondered where these odd configs came from. Removing the hosts torrc
gave  
 ### Unable to load the torrc ###
so arm is trying to read a torrc on the host in the location it knows
which is displayed from the jail, but is ignoring the jail flag.
  Sorry for not getting deeper in this right now.

To Fabian, instead of adding another patch:
Running 'pgrep tor' might show  multiple results, anything containing the string
'tor' will present it's pid.

On 7 it's 'pgrep -x' to get an exact match of the argument ,see man pgrep(1).
   
Thanks for the patches !

 
To all :
The working connection list looks great !


***********************************************************************
To unsubscribe, send an e-mail to majordomo at torproject.org with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/