hi,
coderman wrote (06 Nov 2014 09:55:54 GMT) :
> On 11/6/14, intrigeri <intrigeri@???> wrote:
>> yay! shall I assign #8220 to you, then?
> anon could not log in, but these are the "mixmaster" / "torsocks"
> tickets on my radar:
> "please install mixmaster (or teach us how)" -
> https://labs.riseup.net/code/issues/8225
Replied there, but off-topic as far as this very thread is concerned.
> torsocks in Tails:
> "Prepare a branch that installs torsocks 2.x" -
> https://labs.riseup.net/code/issues/8220
> "Test torsocks 2.0~rc in the context of Tails" -
> https://labs.riseup.net/code/issues/6880
#8220 is a subtask of #6880: to test the thing, we need an ISO first.
> "Have wget directly use the Tor SOCKS proxy" -
> https://labs.riseup.net/code/issues/6623
> "Remove Polipo or replace it with Privoxy" -
> https://labs.riseup.net/code/issues/5379
All current Polipo users that are being migrated to torsocks (see
subtasks of #5379) should be tested with torsocks 2.x. So, I think the
branch for #6880/#8220 you're working on should be based on
feature/5379-remove-polipo.
> "install torsocks" - https://labs.riseup.net/code/issues/5549
Done in Tails 0.12, forget it.
> "Applications audit" - https://labs.riseup.net/code/issues/5769
I think this one can be ignored as far as the migration to torsocks
2.x is concerned.
> it was not clear to me which were old, could be closed, or would need
> to be re-visited in the context of torsocks 2.0. if you think any of
> these can be ignored, please reply so :)
Hoping it helped.
If you really don't want to create yourself a Redmine account, please
at least indicate on each ticket you would normally have assigned to
yourself that you're working on this. Otherwise, I'm pretty sure we'll
see duplicated effort..
Cheers,
--
intrigeri
