Opened 7 months ago

Last modified 2 weeks ago

#28522 new defect

[armhf] (Sandbox) Caught a bad syscall attempt

Reported by: bundesgebaermutter Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.3.4.9
Severity: Normal Keywords: sandbox, armhf, syscall, debian, stretch, 035-backport, 029-backport, postfreeze-ok, 040-can, 033-backport-unreached, 041-can
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hello,

I just come to give the sandbox option in tor´s configuration another try after I had done an update. And learnt that it did not work.

The OS is Debian Stretch on a BananaPi (armhf, 32bit). Kernel is 4.14.70-sunxi armv7l.

Nov 19 17:13:54 eisbaer Tor[11800]: Tor 0.3.4.9 (git-4ac3ccf2863b86e7) running on Linux with Libevent 2.0.21-stable, OpenSSL LibreSSL 2.8.2, Zlib 1.2.8, Liblzma 5.2.2, and Libzstd 1.1.2.
Nov 19 17:13:54 eisbaer Tor[11800]: Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Nov 19 17:13:54 eisbaer Tor[11800]: Read configuration file "/srv/ursus-tor/etc/tor/torrc".
Nov 19 17:13:54 eisbaer Tor[11800]: Based on detected system memory, MaxMemInQueues is set to 748 MB. You can override this by setting MaxMemInQueues by hand.
Nov 19 17:13:54 eisbaer Tor[11800]: Scheduler type KIST has been enabled.
Nov 19 17:13:54 eisbaer Tor[11800]: Opening Control listener on 127.0.0.1:9051
Nov 19 17:13:54 eisbaer Tor[11800]: Opening Control listener on /srv/ursus-tor/var/run/control
Nov 19 17:13:54 eisbaer Tor[11800]: Opening OR listener on 0.0.0.0:8080
Nov 19 17:23:13 eisbaer Tor[11800]: Parsing GEOIP IPv4 file /srv/ursus-tor/etc/tor/geoip.
Nov 19 17:23:16 eisbaer Tor[11800]: Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.

... **without** sandboxing tor starts bootstrapping here ...

Nov 19 17:23:46 eisbaer tor[11800]: ============================================================ T= 1542644626
Nov 19 17:23:46 eisbaer tor[11800]: (Sandbox) Caught a bad syscall attempt (syscall 289)

... according to a syscall list this is "sys_signalfd4" ...

Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(+0x1e5fda)[0x67dfda]
Nov 19 17:23:46 eisbaer tor[11800]: /lib/arm-linux-gnueabihf/libc.so.6(__send+0x17)[0xb6d59278]
Nov 19 17:23:46 eisbaer tor[11800]: /lib/arm-linux-gnueabihf/libc.so.6(__send+0x17)[0xb6d59278]
Nov 19 17:23:46 eisbaer tor[11800]: /lib/arm-linux-gnueabihf/libc.so.6(__vsyslog_chk+0x275)[0xb6d55cea]
Nov 19 17:23:46 eisbaer tor[11800]: /lib/arm-linux-gnueabihf/libc.so.6(syslog+0x17)[0xb6d55e98]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(+0x1d4628)[0x66c628]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(+0x1d49dc)[0x66c9dc]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(log_fn_+0x43)[0x66d150]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(sandbox_getaddrinfo+0x173)[0x67db20]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(tor_addr_lookup+0x155)[0x65915a]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(tor_lookup_hostname+0x23)[0x6628b4]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(resolve_my_address+0x175)[0x5c25e2]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(router_pick_published_address+0x43)[0x55266c]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(router_rebuild_descriptor+0x3f)[0x553340]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(router_get_my_routerinfo_with_err+0x47)[0x55241c]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(router_get_my_routerinfo+0x17)[0x5523b0]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(router_get_my_descriptor+0x15)[0x5524a6]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(init_keys+0x419)[0x5508aa]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(do_main_loop+0x77)[0x50f398]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(tor_run_main+0xff)[0x513084]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(tor_main+0x53)[0x50a4d0]
Nov 19 17:23:46 eisbaer tor[11800]: /srv/ursus-tor/bin/tor(main+0x1d)[0x50a34a]
Nov 19 17:23:46 eisbaer tor[11800]: /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x9d)[0xb6cda4aa]
Nov 19 17:23:47 eisbaer systemd[1]: tor.service: Main process exited, code=exited, status=1/FAILURE
Nov 19 17:23:47 eisbaer systemd[1]: tor.service: Unit entered failed state.
Nov 19 17:23:47 eisbaer systemd[1]: tor.service: Failed with result 'exit-code'.

Child Tickets

Change History (7)

comment:1 Changed 7 months ago by nickm

Keywords: 035-backport 034-backport 033-backport 029-backport added
Milestone: Tor: 0.4.0.x-final

comment:2 Changed 5 months ago by nickm

Keywords: postfreeze-ok added

Mark some tickets as postfreeze-ok, to indicate that I think they are okay to accept in 0.4.0 post-freeze. Does not indicate that they are all necessary to do postfreeze.

comment:3 Changed 4 months ago by dgoulet

Keywords: 040-can added
Priority: MediumLow

Bug triage of 0.4.0 tickets. These are now in the "CAN" section. Lower priority than "040-must".

comment:4 Changed 4 months ago by teor

Keywords: 033-backport removed

These open, non-merge_ready tickets can not get backported to 0.3.3, because 0.3.3 is now unsupported.

comment:5 Changed 4 months ago by teor

Keywords: 033-backport-unreached added

Hmm, I guess they should still get 033-backport-unreached

comment:6 Changed 6 weeks ago by nickm

Keywords: 041-can added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

comment:7 Changed 2 weeks ago by nickm

Keywords: 034-backport removed

Removing 034-backport from all open tickets: 034 has reached EOL.

Note: See TracTickets for help on using tickets.