A few days ago, George posted an invitation for obfsproxy operators to upgrade their Tor software to the latest version on the master branch in the Tor git repo. [1]
I'm running a low traffic obfsbridge on a raspberry pi, the whole thing is rather experimental in its nature already, so decided to try just that.
Presumably everyone for whom this might be relevant already knows these things much better than myself, but since they might be applicable to all/some Debian users (raspberrypi + raspbian/debianÂusers for sure), i'm outlining a couple of snags that can maybe be avoided. Previously I ran 0.2.4.15-rc compiled from deb-src (
http://deb.torproject.org/torproject.org experimental-wheezy main); I think it'd have been the same if a precompiled package had been used. I'd still like to be able to manage Tor via init scripts with as little change as possible, etc.
TL;DR:
- after make && make install, do a whereis tor; in all likelihood, your new version will be atÂ/usr/local/bin/tor, old one atÂ/usr/sbin/tor etc.; /etc/init.d/tor will be using /usr/sbin/tor, so need to change the DAEMON key there
- torrc-defaults will have different values in different distro packages.
cd /usr/local/etc/tor; if there's no torrc there: sudo ln -s /etc/tor/torrc (presumably that's where you kept your torrc before; ~/.torrc should work in any case)
$ ./autogen.sh
if it complains about no aclocal (et al.):
$ sudo apt-get install automake && ./autogen.sh
$ ./configure
$ make
$ sudo make install # or, just use it like that (Tor binary is in src/or/)
If you're using service tor {start,stop,reload,etc}:
$Â/usr/sbin/tor --version;Â/usr/local/bin/tor --version
$ grep DAEMON= /etc/init.d/tor
The latter will likely point to /usr/sbin/tor, which might be outdated (check above).
If that's the case, change that line in init.d/tor to point to the new Tor executable /usr/local/bin/tor - that's where it *should* be; if you don't like that, change
BINDIR = /usr/local/bin
in Tor's Makefile and make install again.
The Debian Tor packages seem to like to assume torrc will be placed in /etc/tor/torrc. If that's where your torrc resides, make a symlink to it from /usr/local/etc/tor, which is where the new Tor executable will look for it.
This is probably an insanely ugly way of dealing with these snags, but if anyone is reserved to upgrade because of things like that, maybe this'll help someone..
Kostas.