[tor-bugs] #28526 [Community/Tor Support]: Document how NGOs can run private obfs4 bridges, and get some doing it
Tor Bug Tracker & Wiki
blackhole at torproject.org
Sun Dec 29 22:00:12 UTC 2019
#28526: Document how NGOs can run private obfs4 bridges, and get some doing it
-------------------------------------------------+-------------------------
Reporter: arma | Owner: ggus
Type: project | Status:
| assigned
Priority: Medium | Milestone:
Component: Community/Tor Support | Version:
Severity: Normal | Resolution:
Keywords: education, documentation, ex- | Actual Points:
sponsor-19, s30-o24a1 |
Parent ID: #31281 | Points:
Reviewer: | Sponsor:
| Sponsor30-must
-------------------------------------------------+-------------------------
Comment (by arma):
Replying to [comment:17 sigvids]:
> Here is a sample full torrc:
>
> {{{
> Log notice file /var/log/tor/log
> ORPort 9001
> AssumeReachable 1
> ExtORPort auto
> BridgeRelay 1
> PublishServerDescriptor 0
> ExitPolicy reject *:*
> ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> ServerTransportListenAddr obfs4 0.0.0.0:443
> ContactInfo yourname at example.com
> Nickname YourBridgeNick
> }}}
Better to say {{{BridgeDistribution none}}} and leave
{{{PublishServerDescriptor}}} at its default. That way your bridge will
publish its statistics in the metrics dataset, but bridgedb won't give it
out. (See comments above.)
Also, setting ExitPolicy reject *:* is redundant with setting BridgeRelay
1, but I guess it can't hurt to still have it there explicitly.
Thanks!
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28526#comment:20>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list