We now have control port filter proxy whiltelist wildcard support. (T445)
(Variable CONTROL_PORT_FILTER_ALLOW_WILDCARDS. It's disabled by default, but by the time it gets enabled for example by users on onionshare or ricochet, we need to know about the security implications.)
This ticket is for researching the security implications.
If we whilte listed the wildcard add_onion *, we don't want it to match some hypothetical feature add_onion * ; .... I.e. not add_onion * ; GETINFO address.
To be researched, if Tor's control protocol actually supports something like ;. If it does, then this would complicate the wildcard feature.
(If it was the case, then we would have to limit the wildcard (*) from example SETCONF HiddenServicePort * to exactly one [numeric] argument etc. Or better, correctly parse multi lined commands.)
Tor Control Protocol description: