Hello, When I run
$ go get git.torproject.org/pluggable-transports/obfs4.git/obfs4proxy $ sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin
on a laptop running linuxmint/ubuntu it produces a nice binary executable. Unfortunately it doesn't work to copy it to the Pi2, because it's not an ARM binary. When I run the same script on the Pi2 I get the following error messages:
go get git.torproject.org/pluggable-transports/obfs4.git/obfs4proxy # git.torproject.org/pluggable-transports/obfs4.git/common/ntor /usr/lib/go/src/pkg/git.torproject.org/pluggable-transports/obfs4.git/common/ntor/ntor.go:272: undefined: sha256.Sum256 /usr/lib/go/src/pkg/git.torproject.org/pluggable-transports/obfs4.git/common/ntor/ntor.go:369: undefined: hmac.Equal # git.torproject.org/pluggable-transports/obfs4.git/common/log /usr/lib/go/src/pkg/git.torproject.org/pluggable-transports/obfs4.git/common/log/log.go:131: function ends without a return statement # git.torproject.org/pluggable-transports/obfs4.git/transports/obfs3 /usr/lib/go/src/pkg/git.torproject.org/pluggable-transports/obfs4.git/transports/obfs3/obfs3.go:278: function ends without a return statement # git.torproject.org/pluggable-transports/obfs4.git/transports/scramblesuit /usr/lib/go/src/pkg/git.torproject.org/pluggable-transports/obfs4.git/transports/scramblesuit/conn.go:322: undefined: hmac.Equal /usr/lib/go/src/pkg/git.torproject.org/pluggable-transports/obfs4.git/transports/scramblesuit/handshake_uniformdh.go:143: undefined: hmac.Equal /usr/lib/go/src/pkg/git.torproject.org/pluggable-transports/obfs4.git/transports/scramblesuit/handshake_uniformdh.go:152: undefined: sha256.Sum256
and the script exits
Any idea how I can get it cleanly on a Pi2? Thanks, J. Chase
tor-relays-request@lists.torproject.org:
Send tor-relays mailing list submissions to tor-relays@lists.torproject.org
To subscribe or unsubscribe via the World Wide Web, visit https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays or, via email, send a message with subject or body 'help' to tor-relays-request@lists.torproject.org
You can reach the person managing the list at tor-relays-owner@lists.torproject.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of tor-relays digest..."
Today's Topics:
- Re: Installing obfs4 on Raspberry Pi bridge (jchase)
- Re: Installing obfs4 on Raspberry Pi bridge (Yawning Angel)
Message: 1 Date: Sun, 12 Apr 2015 17:43:55 +0000 From: jchase jchase@riseup.net To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Installing obfs4 on Raspberry Pi bridge Message-ID: 552AAEDB.4020007@riseup.net Content-Type: text/plain; charset=windows-1252
Hello, Thanks to you I have tor 0.2.5.11 running on a Raspberry Pi2 and obfs4 installed from git. I have good news and bad news. The largest problem is that I get the warning "could not launch managed proxy executable at '/path/obfs4proxy'('Permission denied')" In the past this used to be a problem with apparmor, but apparmor isn't installed. Any idea where I can start looking for a solution? Here are a couple of details and small problems: I didn't install obfs4 directly (due to problems), but installed it to another laptop and copied it to the Pi2 using scp. I have ORPort somewhere above 9000. When I set it to auto, I got a late warning that the port chosen by tor was presenting problems, had I arranged port forwarding, etc.? ExtORPort is "auto" and I get no complaints (probably because obfs4 isn't working). And I have ServerTransportListenAddr obfs3 0.0.0.0:90xx because a lower port, like 80, with port forwarding, received a warning (and didn't work). One thing at a time... Like I asked, where can I look for answers to the obfs4proxy permission denied problem? If I get that fixed, I assume I can play around with the rest until I can use lower ports. Thanks, J Chase
Message: 2 Date: Sun, 12 Apr 2015 20:14:33 +0000 From: Yawning Angel yawning@schwanenlied.me To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Installing obfs4 on Raspberry Pi bridge Message-ID: 20150412201433.6c42f28d@schwanenlied.me Content-Type: text/plain; charset="us-ascii"
On Sun, 12 Apr 2015 17:43:55 +0000 jchase jchase@riseup.net wrote:
Hello, Thanks to you I have tor 0.2.5.11 running on a Raspberry Pi2 and obfs4 installed from git. I have good news and bad news. The largest problem is that I get the warning "could not launch managed proxy executable at '/path/obfs4proxy'('Permission denied')" In the past this used to be a problem with apparmor, but apparmor isn't installed. Any idea where I can start looking for a solution? Here are a couple of details and small problems: I didn't install obfs4 directly (due to problems), but installed it to another laptop and copied it to the Pi2 using scp.
Oh dear. What happens when you run the obfs4proxy executable in a shell directly (on the pi2)?
It should look something like: $ ./obfs4proxy 2015/04/12 20:13:02 [ERROR]: obfs4proxy - must be run as a managed transport
If not, what does 'file /path/obfs4proxy' say?
Regards,
On Thu, 23 Apr 2015 19:53:55 +0000 jchase jchase@riseup.net wrote:
Hello, When I run
$ go get git.torproject.org/pluggable-transports/obfs4.git/obfs4proxy $ sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin
on a laptop running linuxmint/ubuntu it produces a nice binary executable. Unfortunately it doesn't work to copy it to the Pi2, because it's not an ARM binary. When I run the same script on the Pi2 I get the following error messages:
go get git.torproject.org/pluggable-transports/obfs4.git/obfs4proxy # git.torproject.org/pluggable-transports/obfs4.git/common/ntor /usr/lib/go/src/pkg/git.torproject.org/pluggable-transports/obfs4.git/common/ntor/ntor.go:272: undefined: sha256.Sum256
[snip]
Any idea how I can get it cleanly on a Pi2?
This is covered in the README.md:
- Go 1.2.0 or later. Prior versions of Go (Eg: 1.0.2) are missing certain important parts of the runtime library like a SHA256 implementation.
Go 1.2 was released on December 1, 2013, so I'm not particularly inclined to support older versions, especially since it means re-implementing parts of the standard runtime library.
Regards,
tor-relays@lists.torproject.org