In our quantifications of relay diversity, knowing the IP addresses that
traffic exits from is important. Ways to have this information correctly
reported would be very helpful.
-V
On Thu, 14 Jan 2016 at 03:01 grarpamp wrote:
> On Wed, Jan 13, 2016 at 4:27 AM, coderman wrote:
> >>> ... only que
Hi,
I also have concerns about proposal 246, I don't think its benefits are
compelling
compared with the number of drawbacks.
If we do want to skip the introduction point, proposal 252 (single onion
services)
provides a way for onion services to do this on an opt-in basis. (However, it
doesn't
Regarding https://github.com/meejah/txtorcon/pull/155 does anyone have a
good reason not to move txtorcon to using "ipaddress" -- this is a built-in
library on Python3, with backports to Python2.
Thanks,
meejah
___
tor-dev mailing list
tor-dev@lists.tor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
I am not a big fan of prop 246. I don't have a mindblowing counter
argument that it's bad in some way, but I don't like the tradeoffs vs
benefits ratio so much. It is a small performance improvement indeed,
so clients will not cache descripto
On Wed, Jan 13, 2016 at 05:47:03PM +0100, Karsten Loesing wrote:
> Do the Zoossh results there look plausible?
I'm surprised that descriptor parsing is so slow, but I think the
results are plausible, yes. I should look into it.
Thanks,
Philipp
___
tor-
> This was Stem commit c01a9cda4e7699c7f4bd642c8e81ed45aab7a29b and
> Python version 2.7.10.
Great, thanks! Also what was the metrics-lib and zoossh commits?
> Or should we add these performance tests for metrics-lib, Stem, and
> Zoossh to their own repository that also comes with scripts to fetc
On Wed, Jan 13, 2016 at 4:27 AM, coderman wrote:
>>> ... only question is who would have a
>>> compelling use for separating outbound OR connections and outbound
>>> Exit traffic, as per #17975?
>>
>> Bandwidth peering contracts preferential to push or eyeball traffic.
> outbound bind address. Ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/01/16 17:19, Damian Johnson wrote:
> Thanks! Yup, those results look reasonable. I was expecting a
> smaller delta with server/extrainfo descriptors and larger one
> with microdescriptors due to the lazy loading but oh well. What
> stem commit an
On 13/01/16 16:04, Nathan Freitas wrote:
> On Tue, Jan 12, 2016, at 11:52 AM, Michael Rogers wrote:
>> On 12/01/16 16:16, Nathan Freitas wrote:
>>> The broader idea is to determine which Tor torrc settings are relevant
>>> to the mobile environment, and that could use a more intuitive user
>>> inte
Hello there,
we recently finished implementing proposal 250 which is one of the first steps
for the upcoming hidden service redesign [1]. The next steps are implementing
proposal 224 and the other performance and security proposals [2].
On this note, one of the open design issues that we need to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/01/16 16:28, Philipp Winter wrote:
> On Tue, Jan 12, 2016 at 09:40:35AM +0100, Karsten Loesing wrote:
>> Philipp, would you be able to write the Zoossh counterpart for
>> the descriptor types supported by it?
>
> I attached a small tool that sho
On Tue, Jan 12, 2016, at 11:52 AM, Michael Rogers wrote:
> On 12/01/16 16:16, Nathan Freitas wrote:
> > The broader idea is to determine which Tor torrc settings are relevant
> > to the mobile environment, and that could use a more intuitive user
> > interface than the empty text input we currently
On Tue, Jan 12, 2016 at 09:40:35AM +0100, Karsten Loesing wrote:
> Philipp, would you be able to write the Zoossh counterpart for the
> descriptor types supported by it?
I attached a small tool that should do the same thing Damian's script
does for consensuses and server descriptors. Note, howeve
On 1/13/16, grarpamp wrote:
> On Tue, Jan 12, 2016 at 9:58 AM, coderman wrote:
>> ... only question is who would have a
>> compelling use for separating outbound OR connections and outbound
>> Exit traffic, as per #17975?
>
> Bandwidth peering contracts preferential to push or eyeball traffic.
> On 13 Jan 2016, at 20:02, David Goulet wrote:
>
> On 13 Jan (11:34:05), Tim Wilson-Brown - teor wrote:
>>
>>> On 13 Jan 2016, at 01:46, George Kadianakis wrote:
>>>
>>> ...
>>> For what it's worth, we expect this code to run for a long time before the
>>> shared random values generated by t
On 13 Jan (11:34:05), Tim Wilson-Brown - teor wrote:
>
> > On 13 Jan 2016, at 01:46, George Kadianakis wrote:
> >
> > Hello there,
> >
> > we are happy to tell you that we finished coding proposal 250 and our first
> > attempt at implementation is ready for review.
> >
> > You can find the fin
On Tue, Jan 12, 2016 at 9:58 AM, coderman wrote:
> this is the proper situation. only question is who would have a
> compelling use for separating outbound OR connections and outbound
> Exit traffic, as per #17975?
Bandwidth peering contracts preferential to push or eyeball traffic.
_
17 matches
Mail list logo
