Your message dated Thu, 19 Mar 2026 22:58:15 +0100
with message-id <4494422.ejJDZkT8p0@tuxin>
and subject line Re: [Pkg-privacy-maintainers] Bug#941483: torsocks: nc.openbsd
in tight loop when talking to tor via libtorsocks
has caused the Debian Bug report #941483,
regarding torsocks: nc.openbsd in tight loop when talking to tor via libtorsocks
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
941483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941483
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: torsocks
Version: 2.3.0-2+b1
Severity: normal
Control: affects + netcat-openbsd
On my system right now, nc is in a tight loop, burning 100% CPU:
```
0 dkg@alice:~$ strace -p 10348 -T -ttt 2>&1 | head
strace: Process 10348 attached
1569928260.402113 select(4, [3], NULL, NULL, NULL) = 1 (in [3]) <0.000020>
1569928260.402195 recvfrom(3, "", 10, 0, NULL, NULL) = 0 <0.000015>
1569928260.402300 select(4, [3], NULL, NULL, NULL) = 1 (in [3]) <0.000008>
1569928260.402351 recvfrom(3, "", 10, 0, NULL, NULL) = 0 <0.000007>
1569928260.402394 select(4, [3], NULL, NULL, NULL) = 1 (in [3]) <0.000007>
1569928260.402436 recvfrom(3, "", 10, 0, NULL, NULL) = 0 <0.000006>
1569928260.402477 select(4, [3], NULL, NULL, NULL) = 1 (in [3]) <0.000007>
1569928260.402517 recvfrom(3, "", 10, 0, NULL, NULL) = 0 <0.000006>
1569928260.402558 select(4, [3], NULL, NULL, NULL) = 1 (in [3]) <0.000007>
0 dkg@alice:~$ lsof -p 10348
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
nc 10348 dkg cwd DIR 254,3 24576 261633 /home/dkg
nc 10348 dkg rtd DIR 254,1 4096 2 /
nc 10348 dkg txt REG 254,1 43504 135774 /bin/nc.openbsd
nc 10348 dkg mem REG 254,1 51696 141113
/lib/x86_64-linux-gnu/libnss_files-2.29.so
nc 10348 dkg mem REG 254,1 14592 138268
/lib/x86_64-linux-gnu/libdl-2.29.so
nc 10348 dkg mem REG 254,1 1820104 135133
/lib/x86_64-linux-gnu/libc-2.29.so
nc 10348 dkg mem REG 254,1 84808 141227
/lib/x86_64-linux-gnu/libresolv-2.29.so
nc 10348 dkg mem REG 254,1 96568 5752
/usr/lib/x86_64-linux-gnu/libbsd.so.0.10.0
nc 10348 dkg mem REG 254,1 88160 133186
/usr/lib/x86_64-linux-gnu/torsocks/libtorsocks.so.0.0.0
nc 10348 dkg mem REG 254,1 165632 131306
/lib/x86_64-linux-gnu/ld-2.29.so
nc 10348 dkg 0r FIFO 0,12 0t0 8164325 pipe
nc 10348 dkg 1w FIFO 0,12 0t0 8164326 pipe
nc 10348 dkg 2u CHR 136,14 0t0 17 /dev/pts/14
nc 10348 dkg 3u IPv4 8165435 0t0 TCP
localhost:48380->localhost:9050 (CLOSE_WAIT)
0 dkg@alice:~$
```
It was invoked as part of an ssh proxycommand:
torsocks nc jsjr752kjv5evcwv.onion 22
(onion service name is anonymized here)
I tried using ltrace on the same process, but nothing was emitted --
it's doing this loop without crossing any dynamic linker boundaries.
With torsocks-dbgsym and netcat-openbsd-dbgsym installed, and gdb
attached to the process, i see this backtrace:
```
#0 0x00007fb931222187 in __GI___select (nfds=nfds@entry=4,
readfds=readfds@entry=0x7fffa2739eb0, writefds=writefds@entry=0x0,
exceptfds=exceptfds@entry=0x0, timeout=timeout@entry=0x0)
at ../sysdeps/unix/sysv/linux/select.c:41
#1 0x00007fb931359623 in wait_on_fd (fd=3) at socks5.c:40
#2 0x00007fb931359838 in recv_data_impl (fd=3, buf=0x7fffa273a070,
len=<optimized out>) at socks5.c:69
#3 0x00007fb93135a2b0 in socks5_recv_connect_reply
(conn=conn@entry=0x55ca81f32340) at socks5.c:509
#4 0x00007fb931352fca in tsocks_connect_to_tor
(conn=conn@entry=0x55ca81f32340) at torsocks.c:500
#5 0x00007fb9313539e1 in tsocks_connect (sockfd=<optimized out>,
addr=0x55ca81f32320, addrlen=16) at connect.c:206
#6 0x000055ca80745a7c in connect_with_timeout (ctimeout=<optimized out>,
salen=16, sa=0x55ca81f32320, fd=3) at netcat.c:1277
#7 remote_connect (host=0x7fffa273ba37 "jsjr752kjv5evcwv.onion",
port=0x55ca81f321c0 "22", hints=...) at netcat.c:1203
#8 0x000055ca80743ce0 in main (argc=<optimized out>, argv=<optimized out>) at
netcat.c:878
(gdb)
```
Thanks for maintaining torsocks in debian!
--dkg
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (500,
'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages torsocks depends on:
ii libc6 2.29-2
Versions of packages torsocks recommends:
ii tor 0.4.1.6-1
torsocks suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.5.0-6
Hey,
I cannot reproduce the issue with the current version in sid:
torsocks nc mirror.ftp-master.debian.org 22
Feel free to reopen it again, if it is not fixed for you.
Regards,
hefee
--
On Donnerstag, 19. Februar 2026 13:08 Hefee wrote:
> Control: tags -1 +moreinfo +upstream
>
> Hey,
>
> Sorry it took so long for you to get any response.
> Did you retry to use the current version in Trixie? Actually it is an
> upstream issue, so it needs to forwarded to upstream, if the issue isn't
> fixed in meanwhile.
>
> Regards,
>
> hefee
>
> --
>
> On Tue, 01 Oct 2019 07:39:22 -0400 Daniel Kahn Gillmor
> <[email protected]>
> wrote:
> > Package: torsocks
> > Version: 2.3.0-2+b1
> > Severity: normal
> > Control: affects + netcat-openbsd
> >
> > On my system right now, nc is in a tight loop, burning 100% CPU:
> >
> > ```
> > 0 dkg@alice:~$ strace -p 10348 -T -ttt 2>
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
