-----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. > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBCAAGBQJV7SvmAAoJEIN/pSyBJlsR034H/j32IUGpjbSB8AIW6WNOWxPL iNXGqS4KtUFPnPA8Ya6X9Wz3nEwPDl84F2OoiRsxoJ1dFp7DApoNnMtfHxeNVP5x hsdV0c8ph0ttUt97Jng+JvWSJVGs5NEOU8Kmluthr0ZxUSUQimI+7l4imXs1JNN6 4BcsADrIOW1FExefG7itFXcARsBwr7kQD0MRZv8GLWF+vMmFiTGHRVNe5pYg+ii+ sTFQlWI9eAXAoWdwYmTUrZHQiPLrlmMFDFLk0nvKY+AjWseZL6mI/NiDAb8mwNua awy2m4jQA1UHknj+H/cOEh0f+/HGm7vbUK7zhyKZ2R1sOO1ZNZP6cIizJkOQs2E= =Nl0D -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
