-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi,
Thanks for this. But why do you want to run your bridge instance among the same Tor daemon as the one handling Tor Browser?
If you are on Debian, install Tor package separately with apt-get install tor (recommended you add deb.torproject.org to your apt/sources.list file so you get the latest versions all the time - see https://www.sky-ip.org/configure-relay-debian-ubuntu.html )
overwrite the torrc file with this: ORPort 443 ExtORPort auto Nickname <#yourdesirednickname> ContactInfo <#someemailaddresshere> BridgeRelay 1 ExitPolicy reject *:*
While you are at it, you might want to install obf4s4proxy package and provide a pluggable transport bridge. (deb http://deb.torproject.org/torproject.org obfs4proxy main) and add in torrc: ServerTransportPlugin obfs3,obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs3 [::]:<#someport> ServerTransportListenAddr obfs4 [::]:<#someport>
On 9/7/2015 9:11 AM, Kenneth Freeman wrote:
This may be a naïve question, but I've fired up my 64-bit Debian box now that the nights are cool, and editing the torrc to establish a bridge relay borks the browser. I provide anonymity much more than I use it myself, but is the bridge relay copacetic? Thanks in advance.