The Control Proxy, or onion-grater should only have documentation related to its filter, the controller page should have the controller commands, the filter page should have explanation on how to filter, how to allow via profile etc, but not on how to connect.
Also, I fixed a bug recently on tor-ctrl to be able to run from the Workstation, so if you wish to test if a command is filtered or not, you can do through the command line to see what onion-grater lets through.
will be the last one to be done so after the Dev wording is done for the
other pages, the simpler version can contain everything important for the
user in an easy vocabulary
most important to mention onion-grater-add and onion-grater-remove and
onion-grater-list, this is what an user faces with already compatible
source code not so important in the user facing page, maybe just keep it on
the Dev/onio-grater page.
make the footnotes a topic, they are too big to be on the footnotes
maybe merge this page with Dev/Control_Port_Filter_Proxy because the only
filter proxy is onion-grater
I fixed tor-ctrl for the WS, can it be installed by default on the workstation so I can guide to use tor-ctrl on both Workstation and Gateway. The things is that only the tor-ctrl program will work, the others that requires stream, circuits, will be filtered, which is a good job by the onion-grater, but is a program installed that won’t work.
Sure. Just a short mention and link from one to another.
Ah. Yes. If a simpler way works with the cookie, then by all means. Please use the cookie. Probably is like it is before because I didn’t get the idea to research that socat could pass the cookie somehow. Surely that would be much nicer.
Yes. Absolutely can switch to simpler tor-ctrl method.
Due to my native language background and this MediaWiki issue I actually personally prefer proper names starting with a capital letter
Upstream (Tails) decided to use the lower case variant onion-grater. So unless we change the name in Whonix’s for of onion-grater completely, forking the name to only change capitalization would be weird.
It’s only the URL where there is the upper case issue. The page title “onion-grater: a Tor Control Port Filter Proxy” is correct.
Maybe one day we should go for Manual:$wgCapitalLinks - MediaWiki. And then making all links always lower case by default. Writing links by hand is confusing because some letters are sometimes upper case.
So in summary the proper name is onion-grater as named by upstream. The capital O in the page name is considered a bug. It is a MediaWiki issue which is very time consuming to resolve. But by changing the name from lower capitalization to first letter capitalized we’d introduce more bugs.