> On 25 Oct. 2016, at 01:24, René Mayrhofer wrote:
>
> Am 20.10.2016 um 11:34 schrieb teor:
>> We generally track tor features using the Tor bug tracker:
>> https://trac.torproject.org/projects/tor/newticket
>> Use the Core Tor/Tor component.
>>
>> We have found that gitlab is
Am 20.10.2016 um 11:34 schrieb teor:
> We generally track tor features using the Tor bug tracker:
> https://trac.torproject.org/projects/tor/newticket
> Use the Core Tor/Tor component.
>
> We have found that gitlab is useful for making comments on patches.
> But I am also happy to use GitHub, or
> On 2016-09-26 00:54, teor wrote:
>> The one concern I have about this is that Tor-over-Tor would stick out more,
>> as it would look like Tor coming out the OutboundBindAddressExit IP.
>> But we don't encourage Tor-over-Tor anyway.
ToT is technically not some special tor aware / tunneled relay
> On 20 Oct. 2016, at 20:19, René Mayrhofer wrote:
>
> Hi everybody,
>
> Michael Sonntag has extended the patch below to make it configurable and
> tested it on a separate instance here in Linz. Seems to work for our use
> case. If that seems a good option, then we'd like to
Hi everybody,
Michael Sonntag has extended the patch below to make it configurable and
tested it on a separate instance here in Linz. Seems to work for our use
case. If that seems a good option, then we'd like to request review for
upstream inclusion.
> On 26 Sep 2016, at 05:43, René Mayrhofer wrote:
>
>
That is exactly what we have patched our local Tor node to do, although
with a different (slightly hacky, so the patch will be an RFC type)
approach by marking real exit traffic with a ToS flag to leave the
>>> That is exactly what we have patched our local Tor node to do, although
>>> with a different (slightly hacky, so the patch will be an RFC type)
>>> approach by marking real exit traffic with a ToS flag to leave the
>>> decision of what to do with it to the next layer (in our setup Linux
>>>
> On 23 Sep 2016, at 13:02, René Mayrhofer wrote:
>
> Hi everybody,
>
> Unfortunately, it took a bit longer than expected, but here goes...
> FWIW, after the recent update (with subsequent downtime), our exit node
> is fully up and running again (including this patch) and