Tor + Privoxy + OrangePi

В соответсвии с методикой установил TOR и Privoxy на свою апельсинку (Orange Pi plus2e)

$ uname -a
Linux server 3.4.113-sun8i #18 SMP PREEMPT Wed Jan 24 22:10:49 CET 2018 armv7l armv7l armv7l GNU/Linux

Ранее уже проделывал подобную манипуляцию и не раз, но на других платформах (x64-x86) и все работало, но на этот раз возникла проблема. При просмотре статуса службы все как бы выглядело нормально:

$ sudo service tor status
● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
   Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sun 2018-04-22 10:36:26 +05; 23min ago
 Main PID: 627 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/tor.service




Но в syslog сыпалось вот такое:

Apr 22 10:29:00 server systemd[1]: Starting Anonymizing overlay network for TCP...
Apr 22 10:29:01 server tor[8272]: Apr 22 10:29:01.628 [notice] Tor 0.2.9.14 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2g and Zlib 1.2.8.
Apr 22 10:29:01 server tor[8272]: Apr 22 10:29:01.629 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Apr 22 10:29:01 server tor[8272]: Apr 22 10:29:01.629 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Apr 22 10:29:01 server tor[8272]: Apr 22 10:29:01.629 [notice] Read configuration file "/etc/tor/torrc".
Apr 22 10:29:01 server tor[8272]: Configuration was valid
Apr 22 10:29:02 server systemd[8277]: tor@default.service: Failed at step NO_NEW_PRIVILEGES spawning /usr/bin/tor: Invalid argument
Apr 22 10:29:02 server systemd[1]: tor@default.service: Main process exited, code=exited, status=227/NO_NEW_PRIVILEGES
Apr 22 10:29:02 server systemd[1]: Failed to start Anonymizing overlay network for TCP.
Apr 22 10:29:02 server systemd[1]: tor@default.service: Unit entered failed state.
Apr 22 10:29:02 server systemd[1]: tor@default.service: Failed with result 'exit-code'.
Apr 22 10:29:02 server systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
Apr 22 10:29:02 server systemd[1]: Stopped Anonymizing overlay network for TCP.

В русскоязычном сегменте найти решения не получилось и реально рабочих решений, без глубокого осмысления проблемы тоже не искалось. Пока не наткнулся на подобную проблему с mariadb-server ссылка на баг-трекер Debian

Алгоритм решения проблемы

1. Редактируем параметры службы

$ sudo systemctl edit tor@default.service

2.  Заносим следующие параметры

[Service]
PrivateDevices=false
NoNewPrivileges=false

3. Сохраняем

4.  Перезапускаем службу

$ sudo systemctl restart tor@default.service

5. Проверяем лог

$ sudo tail -f /var/log/tor/log

Apr 22 10:46:40.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Apr 22 10:46:42.000 [notice] Bootstrapped 0%: Starting
Apr 22 10:46:43.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Apr 22 10:46:43.000 [notice] Signaled readiness to systemd
Apr 22 10:46:43.000 [notice] Opening Socks listener on /var/run/tor/socks
Apr 22 10:46:43.000 [notice] Opening Control listener on /var/run/tor/control
Apr 22 10:46:45.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Apr 22 10:46:45.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Apr 22 10:46:45.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Apr 22 10:46:45.000 [notice] Bootstrapped 100%: Done