ID: 225PHID: PHID-TASK-zqgthoknptvjzuccjldcAuthor: PatrickStatus at Migration Time: resolvedPriority at Migration Time: Normal
Since we forked tor-controlport-filter by Tails, it might be useful to inform them about the fork. I don’t think they’ll switch to it anytime soon. But perhaps when they need its awesome new features. My experience tells me that they’ll likely, as time permits, will have a cursory look and comment on security and whatnot.
Would you like to be the messenger of the good news or prefer if I did this, @troubadour ? I wouldn’t really mind doing it, I am discussing on their mailinglist various stuff some time now anyhow.
Want you/me to formulate a draft first?
2015-03-08 17:32:32 UTC
I’d prefer if you brought the news to Tails. You are probably more accustomed to their language, and I’m still feeling a little shy. That would be great if they were interested in the development of their original script, and above all, if they could come back with comments on security, or whatnot.
Are there any digests of the numerous Tails mailing lists, like The tor-talk Archives or The tor-dev Archives ? My mail is already crowded with some other lists.
2015-03-08 18:02:32 UTC
Okay. I’ll work on a draft.
I don’t know any useful digests of mailing lists I could work with. The most useful thing could be some (third party) web interface that just shows subjects. Here is tails-dev sorted by subject:https://mailman.boum.org/pipermail/tails-dev/2015-March/subject.html
You could just look into those subjects that are of interest to you. There might be third party mailing list archives that you like better usability wise. And I recommend a separate e-mail account for medium and high volume mailing lists. Additionally I configured my mail client to sort those mails into folders separated by mailing list. I guess it’s impossible to read [not even speaking about grasping] everything on tor-talk and still doing development. It’s just too high traffic.
It would be useful if you were registered on the tails-dev mailing list with such a secondary e-mail account. Then you could make a reply if required without “breaking the thread” [in reference to header].
2015-03-08 18:42:44 UTC
Here is the draft.
Dear Tails developers,
I would like to inform you about the existence of control-port-filter-python, a fork of tor-controlport-filter by Tails.
Improvements:
* Supports parallel connections.
* Configurable by dropping .d-style configuration snippets into /etc/cpfpy.d. I.e. whitelist can be extended by dropping snippets.
* Supports logging.
* Support to answer 'getinfo net/listeners/socks' with the lie '250-net/listeners/socks="127.0.0.1:9150"'.
* Honors signals sigterm, sigint.
* Complete sysvinit script.
* Lintian clean /debian packaging folder.
Code:
https://github.com/Whonix/control-port-filter-python
Main script:
https://github.com/Whonix/control-port-filter-python/blob/master/usr/lib/control-port-filter-python/cpfp.py
Wiki page:
https://www.whonix.org/wiki/Dev/Control_Port_Filter_Proxy
It has been mostly written by troubadoour with some reviewing and testing by me.
We would like to hear your feedback, comments, etc.
A comparison of the three Tor ControlPort filters that exist so far can be found here:
https://www.whonix.org/wiki/Dev/Control_Port_Filter_Proxy#Comparison_of_Control_Port_Filters
Thank you for writing tor-controlport-filter!
Cheers,
Patrick
Any changes you recommend or should I go ahead posting it?
2015-03-08 19:25:46 UTC
Thanks for the tails-dev link, that’s what I was looking for (the archive, not a digest, wrong wording).
Please go ahead posting. It’s more comprehensive than whatever I would have written.
2015-03-09 13:36:15 UTC