[tor-bugs] #11674 [Tor]: Document TOR_PT_PROXY in 'pt-spec.txt'.

[Tor Bug Tracker & Wiki]

#11674: Document TOR_PT_PROXY in 'pt-spec.txt'.
------------------------+-----------------------------
     Reporter:  asn     |      Owner:
         Type:  defect  |     Status:  needs_review
     Priority:  normal  |  Milestone:
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-spec tor-pt
Actual Points:          |  Parent ID:  #8402
       Points:          |
------------------------+-----------------------------

Comment (by dcf):

 "If the pluggable transport proxy detects that the TOR_PT_PROXY
 environment variable is set, it attempts connecting to it." I think anyone
 who has tried implementing this proposal has ignored the "attempts
 connecting to it" part. See for example comment:4:ticket:12125.

 Trying to connect first doesn't make sense in many situations. For
 instance, tor may start up multiple transport plugins but only use one of
 them--they all shouldn't be doing a test probe to the same proxy. Not all
 transports use a single long-lived connection. meek-client is passing its
 proxy configuration on to the browser extension, and it is the browser
 extension that actually connects to the proxy--there's no way to "connect"
 to the proxy at startup.

 I propose wording like
 {{{
 If the value of the TOR_PT_PROXY environment variable is a proxy URL
 usable by the pluggable transport plugin, the plugin writes to stdout:
   PROXY DONE
 Otherwise, it writes
   PROXY-ERROR <errormessage>
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11674#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online