FS#57651 - [linux] Transparent Torification makes tor hang forever
Attached to Project:
Arch Linux
Opened by Robot Anarchy (robotanarchy) - Monday, 26 February 2018, 19:45 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 06 March 2018, 20:35 GMT
Opened by Robot Anarchy (robotanarchy) - Monday, 26 February 2018, 19:45 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 06 March 2018, 20:35 GMT
|
Details
I have transparent torification enabled:
https://wiki.archlinux.org/index.php/Tor#Transparent_Torification With latest kernel update, as soon as the iptables rule gets activated and traffic gets sent ("pacman -Syu" for example), then TOR hangs and does not work anymore. It can not be stopped with systemd or killed, and the PC can't even reboot properly and must be force-shutdown by pressing the power button (ctrl+alt+del a few times makes systemd say it will do a force shutdown, but it is still stuck). This is with the current linux-hardened and linux-lts packages. After downgrading the linux-hardened package to 4.15.5.a-1 again, it works as expected again. When TOR was stuck, the kernel reported that it hang more than 120 seconds or so, and told me how I could disable that message. I can get the full message if required. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Tuesday, 06 March 2018, 20:35 GMT
Reason for closing: Fixed
Additional comments about closing: linux 4.15.7
Tuesday, 06 March 2018, 20:35 GMT
Reason for closing: Fixed
Additional comments about closing: linux 4.15.7
Comment by Doug Newgard (Scimmia) -
Thursday, 01 March 2018, 14:40 GMT
Comment by
Robot Anarchy (robotanarchy) -
Friday, 02 March 2018, 20:10 GMT
Comment by loqs (loqs) - Friday, 02
March 2018, 20:31 GMT
Comment by nil0x42 (nil0x42) -
Monday, 05 March 2018, 00:43 GMT
Comment by loqs (loqs) - Monday, 05
March 2018, 12:40 GMT
Comment by
Robot Anarchy (robotanarchy) -
Tuesday, 06 March 2018, 20:32 GMT
Does it work with the normal, stock "linux" kernel?
Tested now, same issue with stock "linux" kernel.
The issue is still present in linux 4.15.7-1 in testing and
linux-hardened 4.15.7.a-1 in community?
i have exactly the same problem, even with standard linux package
(not the hardened one)
@nil0x42 Is the issue still present in linux 4.15.7-1 in testing
and linux-hardened 4.15.7.a-1 in community?
It is fixed for me in both linux-hardened 4.15.7a-1 and in linux
4.15.7-1 (not in testing anymore)!