>
> On 16 Nov 2017, at 00:38, Alec Muffett wrote:
>
>> I think it's important to point out that a Tor client is never
>> guaranteed to hold a *definitive* consensus.
>>
> That's why I say "(mostly) definitive" in my text - my feeling is that a
> locally-held copy of the consensus to be queried
On Mon, Oct 30, 2017 at 3:57 PM, David Goulet wrote:
> Hello everyone!
>
> DISCLAIMER: The following is enormous and tries to describe in some level
> of
> details the situation in tor with connection<->channel<->scheduler. This
> comes
> after we've merged the KIST scheduler, we've realized many
On Wed, Nov 15, 2017 at 10:03:39AM -0600, Tom Ritter wrote:
> Detecting exit nodes is error prone, as you point out. Some exit nodes
> have their traffic exit a different address than their listening
> port.[1]
Right. It's not trivial for tor to figure out what exit relays are
multi-homed -- at l
On Tue, Nov 14, 2017 at 02:51:55PM +0200, George Kadianakis wrote:
> Let me know what you think :)
Section 9.4 in the Alt-Svc draft talks about abusing the header for
tracking. In particular, a malicious website could give each Tor user
a unique onion domain to track their activity. That's parti
On 15 November 2017 at 05:35, Alec Muffett wrote:
> Apologies, I am waiting for a train and don't have much bandwidth, so I will
> be brief:
>
> 1) There is no point in issuing to anyone unless
> they are accessing via an exit node.
>
> 2) It's inefficient to issue the header upon every web acce
I think it's important to point out that a Tor client is never
guaranteed to hold a *definitive* consensus.
That's why I say "(mostly) definitive" in my text - my feeling is that a
locally-held copy of the consensus to be queried is going to be on average
of far higher quality, completeness, and
Alec Muffett writes:
> On 15 Nov 2017 12:18, "Iain R. Learmonth" wrote:
>
> Is this not what TorDNSEL does?
> https://www.torproject.org/projects/tordnsel.html.en
>
>
> Hi Iain!
>
Hey Alec,
thanks for the feedback.
> That certainly sounds like it will give you the answer! But although it
> wo
George Kadianakis writes:
> Hey Tim,
>
OK updates here.
We merged #23895 and #23862 to 032 and master.
#23817 is now in needs_review and hopefully will get in the next 032 alpha.
I think this next alpha should be much better in terms of mds.
Next tickets in terms of importance should probably
On 15 Nov 2017 12:18, "Iain R. Learmonth" wrote:
Is this not what TorDNSEL does?
https://www.torproject.org/projects/tordnsel.html.en
Hi Iain!
That certainly sounds like it will give you the answer! But although it
would give the right kind of answer, it is not what I am asking for.
At the sc
Hi,
On 15/11/17 11:35, Alec Muffett wrote:
> 8) So, to pass concrete advice on the basis of experience: rather than
> pursue novel headers and reinvent a bunch of established,
> widely-understood web redirection technologies, I would ask that Tor
> focus its efforts instead upon providing a servic
Apologies, I am waiting for a train and don't have much bandwidth, so I
will be brief:
1) There is no point in issuing to anyone unless
they are accessing via an exit node.
2) It's inefficient to issue the header upon every web access by every
person in the world; when the header is only releva
Tom Ritter writes:
> I am a big proponent of websites advertising .onions in their Alt-Srv.
>
>> 4.2. No security/performance benefits
>>
>>While we could come up with auto-redirect proposals that provide security
>>and performance benefits, this proposal does not actually provide any of
12 matches
Mail list logo
