[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9957 [Tor]: Tor should consider stderr output of transport proxies

#9957: Tor should consider stderr output of transport proxies
------------------------+--------------------------------
     Reporter:  wfn     |      Owner:
         Type:  defect  |     Status:  needs_review
     Priority:  minor   |  Milestone:  Tor: 0.2.6.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-pt
Actual Points:          |  Parent ID:
       Points:          |
------------------------+--------------------------------

Comment (by wfn):

 Rebased once again (same branch) - to include an additional change which
 includes the `report_proxy_stderr` keyword that a user can look for when
 inspecting INFO-level tor log:

 https://github.com/wfn/tor/compare/bug_9957_2 ->

   *
 https://github.com/wfn/tor/commit/9b3ef629225fa3a0fea0a7090a3ee8a4b14ffab1
   *
 https://github.com/wfn/tor/commit/f8152a1fd36e5944ccf604a74bfbbb776e791786

 Also, re: my
 > (btw, you'll notice that the proxy name comes out to be the path to the
 python executable - but that's unavoidable in this case and happens at
 other parts in the log, too, because pt->argv[0]. Figuring out which
 argument is an actual argument and which one is part of the proxy call is
 probably a hairy thing, or impossible.)

 (the first argument is the path to the python executable because I have a
 custom executable with modified CAPabilities, etc. Normally `pt->argv[0]`
 does show a meaningful PT proxy name.)

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9957#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs