[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #11090 [Core Tor/Torsocks]: torsocks should log errors to stderr and not stdout
#11090: torsocks should log errors to stderr and not stdout
-------------------------------+-----------------------------------
Reporter: infinity0 | Owner: dgoulet
Type: defect | Status: needs_information
Priority: Medium | Milestone:
Component: Core Tor/Torsocks | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------+-----------------------------------
Changes (by dgoulet):
* status: assigned => needs_information
* severity: => Normal
Comment:
I can confirm that torsocks does write errors on `stderr` with the gpg
test case in last comment:
{{{
16512 write16512 write(2, "[Jun 13 17:19:04] PERROR torsock"..., 120) =
120 (2, "[Jun 13 17:19:04] PERROR torsock"..., 120) = 120
}}}
So I think here the issue is a multi process one. In the strace I see that
gpg calls:
{{{
16512 execve("/usr/lib/gnupg/gpgkeys_hkp", ["/usr/lib/gnupg/gpgkeys_hkp"],
[/* 56 vars */] <unfinished ...>
}}}
... and for that process, `2>/dev/null` seems to not being applied. That's
possibly an issue with torsocks that is the redirection to devnull is not
given to the `gpg` process (maybe?)...
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11090#comment:14>
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