Re: [tor-bugs] #28181 [Core Tor/Tor]: spec: Add to pt-spec.txt control messages going back to main process (tor)

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

#28181: spec: Add to pt-spec.txt control messages going back to main process (tor)
-------------------------------------------------+-------------------------
 Reporter:  dgoulet                              |          Owner:  dgoulet
     Type:  enhancement                          |         Status:
                                                 |  assigned
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.3.6.x-final
Component:  Core Tor/Tor                         |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tor-spec, tor-pt, 036-roadmap-       |  Actual Points:
  subtask                                        |
Parent ID:  #28180                               |         Points:
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor8
-------------------------------------------------+-------------------------

Comment (by dgoulet):

 Then we should simply go with `LOG <msg>` and ONLY in the PT 1.0 spec for
 now... I would prefer the PT 2.0 community to cherry pick this if they
 want and maybe improve but at least have a better discussion/analysis of
 this feature.

 It seems, without much more work, we can't really come up with a simple
 format that will apply to all current and future PTs. And, as you mention,
 the `level` is quite "Tor specific" and we (ahf and I) think it is a bad
 idea to require an PT to have knowledge of the tor's log level.

 The `<msg>` should be PT specific that is the format is decided by the PT
 itself like obfs4 might decide to have one format and meek another.

 In other words, for logging (which is what LOG is), Tor shouldn't care
 about the content of `<msg>` and simply log it at INFO level and send it
 to the control port with something like `PT_LOG <transport> <msg>` event
 (Tor knows what is the transport internally).

 I believe you are also right that we are not fixing the "connection issue"
 and thus should go with the SOCKS event instead.

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