So far I have been building tor packages myself on the Pi, but your post
made me check out out the repositories again.
Unfortunately, it's still a bit of a mess:
- The Tor Project repo has "armhf" builds only for old Tor versions, and
I'm not sure if they are even meant for the Pi's processor (
Thanks for your answer.
Your instructions were good and explicit, but you hit on two of the
problems I run into. I installed tor 0.2.5.11-1 from torproject.org and
got two error messages that I couldn't solve. I would have to go back
and re-install 0.2.5.11-1 to tell you what they were. In any case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
J - those links are for reference only. They cannot be added in
sources.list file because they are not valid repository strings.
Here is what I've learned so far.
If you are on Raspberry Pi B/B+ (ARMv6 CPU) you will not be fully
compatible with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I wanted to know whether a particular OS tends to be more likely
running outdated* tor releases than another.
In case others are interested as well, here is the answer.
OSX, OpenBSD and Windows are more likely running outdated tor releases
than Fre
On Mon, 30 Mar 2015 01:02:25 +0300
s7r wrote:
> We currently do not have armhf or armel packages for obfs4proxy in
> deb.torproject.org, but Yawning (CC'ed) will let us know when he has
> time how we can build obfs4proxy from git on Raspbian.
Hmm, wonder why there aren't new packages. IIRC there
