Package: tor
Version: 0.3.3.7-1
Severity: normal
Tags: patch upstream

Dear Maintainer,

when trying to run an instance of Tor with a custom config file, e.g.
tor -f ~/myconf, it will fail due to a (buggy) seccomp filter:

============================================================ T= 1531579290
(Sandbox) Caught a bad syscall attempt (syscall openat)
tor(+0x1a689a)[0x56184d39189a]
/lib/x86_64-linux-gnu/libpthread.so.0(open64+0x4b)[0x7f548fb333ab]
/lib/x86_64-linux-gnu/libpthread.so.0(open64+0x4b)[0x7f548fb333ab]
tor(tor_open_cloexec+0x40)[0x56184d377920]
tor(start_writing_to_file+0x17a)[0x56184d38b39a]
tor(+0x1a047b)[0x56184d38b47b]
tor(+0x1a05c8)[0x56184d38b5c8]
tor(or_state_save+0x15b)[0x56184d2a97ab]
tor(+0x5497b)[0x56184d23f97b]
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x229ba)[0x7f5490d549ba]
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x5a7)[0x7f5490d55537]
tor(do_main_loop+0x2b4)[0x56184d2406f4]
tor(tor_run_main+0x1025)[0x56184d242bd5]
tor(tor_main+0x3a)[0x56184d23b18a]
tor(main+0x19)[0x56184d23af19]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f548f585a87]
tor(_start+0x2a)[0x56184d23af6a]

The fix [1] mentioned in the discussion of the bug on Tor's bugtracker [2] 
solves the problem.


Regards, Jan


PS: I'm unsure whether bugs like this are supposed to be reported here. My 
apologies if they shouldn't be. However, I figured it will 1) help others 
encountering the bug and 2) make sure the package maintainer is aware of it.

[1] 
https://github.com/Jigsaw52/tor/commit/9ec292e1c45a522a7d3b3c9a1c2630bf05047990
[2] https://trac.torproject.org/projects/tor/ticket/25440


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tor depends on:
ii  adduser         3.117
ii  libc6           2.27-3
ii  libcap2         1:2.25-1.2
ii  libevent-2.1-6  2.1.8-stable-4
ii  liblzma5        5.2.2-1.3
ii  libseccomp2     2.3.3-3
ii  libssl1.1       1.1.0h-4
ii  libsystemd0     239-5
ii  libzstd1        1.3.4+dfsg-3
ii  lsb-base        9.20170808
ii  zlib1g          1:1.2.11.dfsg-1

Versions of packages tor recommends:
ii  logrotate    3.11.0-0.1
ii  tor-geoipdb  0.3.3.7-1
pn  torsocks     <none>

Versions of packages tor suggests:
pn  apparmor-utils       <none>
pn  mixmaster            <none>
pn  obfs4proxy           <none>
ii  socat                1.7.3.2-2
pn  tor-arm              <none>
pn  torbrowser-launcher  <none>

-- Configuration Files:
/etc/tor/torrc changed [not included]

-- no debconf information

Reply via email to