#30471: Improve UX for obfs4 bridge operation
 Reporter:  arma                     |          Owner:  (none)
     Type:  project                  |         Status:  new
 Priority:  Medium                   |      Milestone:
Component:  Circumvention/Obfs4      |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:  anti-censorship-roadmap  |  Actual Points:
Parent ID:                           |         Points:
 Reviewer:                           |        Sponsor:

Comment (by phw):

 [https://trac.torproject.org/projects/tor/ticket/30441#comment:10 Over
 here], I emailed several bridge operators whose obfs4 port was not
 reachable. The ones who got back to me all had one of the following two

 * Several people thought that only the ORPort must be reachable. They
 didn't know that obfs4 needs a separate port. We need to make this clear
 in our documentation.
 * Some people have obfs4 listen on a locally-scoped address.
 [https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt#n305 Our spec]
 says that this is fine but it doesn't seem to work in practice because Tor
 ends up writing the locally-scoped address into its descriptor, e.g.:
 `transport obfs4`. This looks like a bug. I don't think a
 locally-scoped address should ever end up in a descriptor.

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30471#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
tor-bugs mailing list

Reply via email to