[tor-bugs] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Aug 13 01:01:07 UTC 2019
#29128: Place complete obfs4 bridge line in accessible location
-------------------------------------------------+-------------------------
Reporter: phoul | Owner: (none)
Type: defect | Status:
| needs_information
Priority: Medium | Milestone: Tor:
| unspecified
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-pt, tor-doc, | Actual Points:
040-deferred-20190220 |
Parent ID: #30471 | Points:
Reviewer: | Sponsor:
| Sponsor28
-------------------------------------------------+-------------------------
Comment (by phw):
Replying to [comment:9 nickm]:
> Is there a standardized way for Tor to learn from the PT which fields it
should put in the Bridge line? It knows the `fingerprint`, and it has a
good guess about the `address` field (though the PT may want to override
that), but it usually needs the PT's help to learn the `port` and any
other fields.
[[br]]
I believe that all we need is in the `SMETHOD` line that Tor reads from
the PT proxy's stdout. Our [https://gitweb.torproject.org/torspec.git/tree
/pt-spec.txt#n544 pt-spec.txt] documents its format as:
{{{
SMETHOD <transport> <address:port> [options]
}}}
Note that `[options]` will need a bit of processing because
[https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt#n555 it's
currently defined] as `ARGS:[<Key>=<Value>,]+[<Key>=<Value>]`.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29128#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list