onionshare, ricochet, etc. would need something like this.
CONTROL_PORT_FILTER_WHITELIST=PROTOCOLINFO 1,add_onion *,del_onion *
So it would be nice if we had a wildcard matching feature. So stuff like:
All would be accepted.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Invalid | Patrick | T444 test if Ricochet IM instructions are functional | ||
| Resolved | troubadour | T445 CONTROL_PORT_FILTER_WHITELIST wildcard feature | ||
| Resolved | Patrick | T446 research control port filter proxy whiltelist wildcard security implications |
Some interesting projects that are related:
https://lists.torproject.org/pipermail/tor-dev/2015-December/010049.html
https://lists.torproject.org/pipermail/tor-dev/2015-December/010051.html
troubadour has implemented this.
Add wildcard support New variable CONTROL_PORT_FILTER_ALLOW_WILDCARDS. If set, commands containing random data (ex hidden service ID:port) are passed if an wildcard alias exists in the commands whitelist (ex 'add_onion *')
https://github.com/Whonix/control-port-filter-python/commit/96a8c164e44269c7ffd9e8c715b92a84f3359c59