Keeping message Tor control panel Tor Status = Connected to the Tor network is confusing as it doesn’t reflect the actual state. Users expect this to be updated in real time when they open tor-control-panel.
I was looking into tor-control-panel, because it could serve as base for safely editing the tor configuration files.
I am far from ready to contribute to Qt applications but I have some ideas to do long term:
let the user edit the torrc with a gui text editor after clicking on the Files (Logs) → torrc. Then it could verify the file and give 3 options → edit again, exit without saving, force save configuration. A gui for vitor
would very much like to use this on plain debian, and it currently breaks because it is creating unreadable files on /etc/torrc.d and /usr/local/etc/torrc.d. I read the thread, but I still find creating this folder uncessesary for plain debian, it does not work anyway.
it could be a gui send command for tor-ctrl, so user types commands directly on tor-control-panel and see responses on a qt application also.
Anyway, don’t put much hope as I am still learning and this is not my priority.
user@host:~$ tor-control-panel
/usr/lib/python3/dist-packages/tor_control_panel/tor_bootstrap.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="?
if self.tor_controller.get_conf('DisableNetwork') is '1':
Adding that folder through ACW / TCP would lead to AppArmor issues and therefore Tor failing to start.
ACW / TCP requires that. An alternative would be directly modifying /etc/tor/torrc but that is complex, error-prone. Therefore I won’t implement that. /etc/torrc.d/*.conf drop-in folder is in my opinion sustainable way forward.
Even if Debian supported /etc/torrc.d/*.conf drop-in folder, Whonix uses /usr/local/etc/torrc.d/*.conf for Qubes(-Whonix) support. Supporting both, /etc/torrc.d and /usr/local/etc/torrc.d folders would also make the code more complex, more time consuming to implement, test. Given that there are no co-maintainers investing brain power into this, Debian (non-Kicksecure) support probably won’t happen.
Kicksecure support is possible. For that the GitHub - Whonix/anon-gw-anonymizer-config (which handles the required AppArmor modifications to allow Tor reading /etc/torrc.d and /usr/local/etc/torrc.d folders) needs to be ported to Kicksecure which will happen at a later time. The name of that package might become anonymizer-config-dist or so. Debian (non-Kicksecure) users being OK with folder /usr/local/etc/torrc.d and installing anonymizer-config-dist could then even use ACW / TCP.
ACW / TCP in the future will probably depend on anonymizer-config-dist.