Re: [tor-bugs] #10629 [Tor]: PT spec changes for better interoperability with other projects

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#10629: PT spec changes for better interoperability with other projects
-----------------------------+-----------------------
     Reporter:  infinity0    |      Owner:  infinity0
         Type:  enhancement  |     Status:  assigned
     Priority:  normal       |  Milestone:
    Component:  Tor          |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------------

Comment (by dcf):

 Replying to [comment:8 asn]:
 > - Logging support. It's not clear how obfsproxy/etc. opreators are
 supposed to do logging atm, and it's not clear where the log file should
 be written. Solutions here include passing the log messages to Tor
 somehow, or forcing PTs to implement syslog support (or log in
 `pt_state`), or something like that.

 Apart from the question of where to write log files, it would be very nice
 if transports could tell tor to log something (so that it will end up in
 the log that Tor Launcher copies to the clipboard, for example).

 tor keeps the stdout of each plugin process open; how about we add
 commands like
 {{{
 LOG DEBUG Received SOCKS connection.
 LOG WARN Unable to find any foobars, this transport probably won't work.
 }}}
 tor could then copy those lines into its own log, prefixed by the
 transport name.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10629#comment:10>
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