[tor-bugs] #24759 [Core Tor/Tor]: (Sandbox) Caught a bad syscall attempt (syscall socket)

Tor Bug Tracker & Wiki blackhole at torproject.org
Thu Dec 28 23:29:41 UTC 2017


#24759: (Sandbox) Caught a bad syscall attempt (syscall socket)
------------------------------+--------------------------
     Reporter:  mig5          |      Owner:  (none)
         Type:  defect        |     Status:  new
     Priority:  Medium        |  Milestone:
    Component:  Core Tor/Tor  |    Version:  Tor: 0.3.1.9
     Severity:  Normal        |   Keywords:  sandbox
Actual Points:                |  Parent ID:
       Points:                |   Reviewer:
      Sponsor:                |
------------------------------+--------------------------
 Hi,

 With the following torrc I experience the subsequent trace:

 {{{
 Sandbox 1
 DataDirectory /tmp/tmp2z5k8mqz
 SocksPort 32609
 ControlSocket /tmp/tmp2z5k8mqz/control_socket
 CookieAuthentication 1
 CookieAuthFile /tmp/tmp2z5k8mqz/cookie
 AvoidDiskWrites 1
 Log notice stdout
 GeoIPFile /usr/share/tor/geoip
 GeoIPv6File /usr/share/tor/geoip6
 }}}

 {{{
 [user at host tmp2z5k8mqz]$ tor -f torrc
 Dec 29 10:24:05.125 [notice] Tor 0.3.1.9 (git-727d3f1b5e6eeda7) running on
 Linux with Libevent 2.0.22-stable, OpenSSL 1.1.0g-fips, Zlib 1.2.11,
 Liblzma N/A, and Libzstd N/A.
 Dec 29 10:24:05.125 [notice] Tor can't help you if you use it wrong! Learn
 how to be safe at https://www.torproject.org/download/download#warning
 Dec 29 10:24:05.125 [notice] Read configuration file
 "/tmp/tmp2z5k8mqz/torrc".
 Dec 29 10:24:05.128 [notice] Opening Socks listener on 127.0.0.1:32609
 Dec 29 10:24:05.128 [notice] Opening Control listener on
 /tmp/tmp2z5k8mqz/control_socket
 Dec 29 10:24:05.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
 Dec 29 10:24:05.000 [notice] Parsing GEOIP IPv6 file
 /usr/share/tor/geoip6.
 Dec 29 10:24:05.000 [notice] Bootstrapped 0%: Starting
 Dec 29 10:24:06.000 [notice] Starting with guard context "default"
 Dec 29 10:24:06.000 [notice] Bootstrapped 5%: Connecting to directory
 server

 ============================================================ T= 1514503447
 (Sandbox) Caught a bad syscall attempt (syscall socket)
 tor(+0x1853fa)[0x56068ff303fa]
 /lib64/libc.so.6(socket+0x7)[0x7893d9664fb7]
 /lib64/libc.so.6(socket+0x7)[0x7893d9664fb7]
 /lib64/libc.so.6(+0x12e3fa)[0x7893d96813fa]
 /lib64/libc.so.6(+0x12e4f1)[0x7893d96814f1]
 /lib64/libc.so.6(getifaddrs+0x10)[0x7893d9682230]
 tor(get_interface_addresses_raw+0x3c)[0x56068ff13eec]
 tor(get_interface_address6_list+0x30)[0x56068ff14620]
 tor(get_interface_address6+0x45)[0x56068ff14875]
 tor(+0x109378)[0x56068feb4378]
 tor(connection_handle_write+0x2e)[0x56068feb44ae]
 tor(+0x4d5ce)[0x56068fdf85ce]
 /lib64/libevent-2.0.so.5(event_base_loop+0x7a9)[0x7893da6943f9]
 tor(do_main_loop+0x29d)[0x56068fdf978d]
 tor(tor_main+0xe25)[0x56068fdfc5a5]
 tor(main+0x19)[0x56068fdf5009]
 /lib64/libc.so.6(__libc_start_main+0xea)[0x7893d957388a]
 tor(_start+0x2a)[0x56068fdf505a]
 }}}

 It of course works with Sandbox 0.

 Is there something in my config that is incompatible with the Sandbox
 mode?

 Maybe related to 16579 except syslog is not the issue here.

 Thanks!

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


More information about the tor-bugs mailing list