[tor-bugs] #8585 [Core Tor/Torsocks]: Figure out why weechat+ssl don't play nice with torsocks

[Tor Bug Tracker & Wiki]

#8585: Figure out why weechat+ssl don't play nice with torsocks
-------------------------------+-------------------------
 Reporter:  sysrqb             |          Owner:  sysrqb
     Type:  defect             |         Status:  closed
 Priority:  Medium             |      Milestone:
Component:  Core Tor/Torsocks  |        Version:
 Severity:  Normal             |     Resolution:  wontfix
 Keywords:                     |  Actual Points:
Parent ID:                     |         Points:
 Reviewer:                     |        Sponsor:
-------------------------------+-------------------------
Changes (by dgoulet):

 * status:  assigned => closed
 * resolution:   => wontfix
 * severity:   => Normal


Comment:

 Ok I took a quick look and this is because of multi process. It seems that
 the DNS resolution is done in a separate process, then connection to it as
 well. Once it's all good, that process passes it back to the main process
 through Unix socket FD passing which is something torsocks denies because
 there is no way we can really confirm that we did open that socket through
 Tor.

 This to be fixed would require torsocks to support multi process which is
 very tricky. Irssi has a similar issue when resolving .onion where DNS
 resolution is done in a new process and the .onion pool is not shared
 between processes (#11727). Until we have a multi process support (shared
 memory or something), we won't be able to fix this. Closing in favor of
 the multi process ticket.

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