[Whonix-devel] [Tails-dev] Tails control port filter proxy in Whonix?

Patrick Schleizer patrick-mailinglists at whonix.org
Wed Jan 11 23:26:00 CET 2017

Happy to report, that a few profiles have been successfully written.
That are using Whonix forked config parsing code.

They are now living here:


There is one for onionshare, one for ricochet as well as one for
ZeroNet. So onionshare and ricochet will most likely run fine in the
next version of Whonix, Whonix 14.

I am impressed by the rewrite functionalities which are a blessing.
Ricochet does something rather ugly, requesting several GETINFO status
at once.

GETINFO status/circuit-established status/bootstrap-phase

With Tails control port filter proxy, these are elegantly rewritten.

      - pattern: 'status/circuit-established status/bootstrap-phase
        - pattern:     '250-status/bootstrap-phase=*'
          replacement: '250-status/bootstrap-phase=NOTICE BOOTSTRAP
        - pattern:     '250-net/listeners/socks=".*"'
          replacement: '250-net/listeners/socks=""'

The ZeroNet profile latter however might require some more hackery. Or
fixes in ZeroNet or fixes in the control port filter proxy. This is
probably because ZeroNet has custom code for Tor control protocol
authentication. Not using python-stem. ZeroNet works when having a
direct Tor control connection but not through the control port filter proxy.

- https://github.com/HelloZeroNet/ZeroNet/blob/master/src/Tor/TorManager.py

Reported two issues.

- https://github.com/HelloZeroNet/ZeroNet/issues/756
- https://github.com/HelloZeroNet/ZeroNet/issues/758

Best regards,

More information about the Whonix-devel mailing list