Note (for PyPI or development installs) you’ll need to install
liblzma development libraries. How to do this on
various architectures (please send missing ones!):
- Debian + Ubuntu:
apt-get install build-essential python-dev python-virtualenv libffi-dev liblzma-dev.
Once you have libraries installed as above, you should be able to do a
pip install carml. It’s also possible to point to the
.whl file (e.g. after signature verification).
It is recommended to use
virtualenv to try without affecting
virtualenv venv . ./venv/bin/activate pip install carml
From a fresh clone (
git clone https://github.com/meejah/carml.git)
make venv. Then activate your new virtualenv with
./venv/bin/activate and then
pip install --editable . which
should install all the dependencies (listed in
To do this and use
peep, you need pip version 6.1.1. So, you you
can try something like this (from the root of a fresh clone):
virtualenv venv . ./venv/bin/activate pip install --upgrade pip setuptools # esp. for Debian pip install --editable .
For Tor setup, make sure you have at least the following in
CookieAuthentication 1 CookieAuthFileGroupReadable 1 ControlPort 9051 # corresponding carml option: "--connect tcp:127.0.0.1:9051"
Or, if you prefer Unix sockets (recommended):
CookieAuthentication 1 ControlSocketsGroupWritable 1 ControlSocket /var/run/tor/control # corresponding carml option: "--connect unix:/var/run/tor/control"
The port or unix-socket can obviously be whatever; the above are Tor’s defaults on Debian. The Tor Browser Bundle defaults to using 9151 for the control socket (and DOES use cookie authentication by default).
On Debian/Ubuntu you need to be part of the
debian-tor group. To
groups and verify
debian-tor is on the list. If
not, add yourself (as root, do):
# usermod username --append --groups debian-tor
If you changed Tor’s configuration, don’t forget to tell it (as root):
# service tor reload