-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24.03.2014 13:57, George Kadianakis wrote:
> Replying to some new additions in the proposal:
>
>> Thanks asn! "Ask help from organizations that are crawling" Today
>> I emailed to duckduckgo and asked is there an easy way to search
>> new .onions u
On Thu, Mar 13, 2014 at 10:21:38PM +, George Kadianakis wrote:
> From {2}, we see that the Tor network has 6000MiB/s advertised guard
> bandwidth (orange line), but supposedly is only using the 3500MiB/s
> (yellow line). This means, that supposedly we are only using 3/5ths of
> our guard capaci
Roger Dingledine:
> On Tue, Mar 25, 2014 at 01:41:43PM -0700, Mike Perry wrote:
> > Nicholas Hopper:
> > > I modified Aaron Johnson's TorPS simulator to
> > > simulate 50K clients
>
> > ** The reason I ask is because I suspect there is actually an interplay
> > between the current circuit build t
On Tue, Mar 25, 2014 at 01:41:43PM -0700, Mike Perry wrote:
> Nicholas Hopper:
> > I modified Aaron Johnson's TorPS simulator to
> > simulate 50K clients
> ** The reason I ask is because I suspect there is actually an interplay
> between the current circuit build timeout code and the pool of 3 gu
Nicholas Hopper:
> On Thu, Mar 13, 2014 at 5:21 PM, George Kadianakis
> wrote:
> > tl;dr: analysis seems to indicate that switching to one guard node
> > might not be catastrophic to the performance of Tor. To improve
> > performance some increased guard bandwidth thresholds are proposed
> > that
On Thu, Mar 13, 2014 at 5:21 PM, George Kadianakis
wrote:
> tl;dr: analysis seems to indicate that switching to one guard node
> might not be catastrophic to the performance of Tor. To improve
> performance some increased guard bandwidth thresholds are proposed
> that seem to help without complet
This is probably due to newer auto-tools having slightly different
configuration options. On a recent setup, the following occured:
make[2]: arm-eabi-/opt/android-ndk/[...]/arm-linux-androideabi-gcc: Command not
found
It was, for some reason, making CC be arm-eabi- plus the path to the NDK.
For
> After the weekend is fine. The next deadline, as I understand, is April
> 5 at which point we (Tor people) need to have all the proposals
> ranked. So, your final proposal would need to be ready some time before
> that (say, end of March latest) as we need time to put together final
> rankings (w
E M writes:
> I don't really know the "moving" pace you expect me to have, so I
> safely draft the final/desired proposal in time, so I would appreciate
> if my pace is no up to your expectations, to let me know so I could
> adapt accordingly.
After the weekend is fine. The next deadline, as I u
Hi Einnhverr. Moving this to tor-dev@ since you intended to but got
the wrong address (it's tor-dev@lists.torproject.org). If you're not
already subscribed to it then please do so at...
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Cheers! -Damian
On Tue, Mar 25, 2014 at 4:36 AM,
Hi, all.
This is another developer's meeting for working on the program "tor".
(This won't cover all the other programs developed under the Tor
umbrella.)
We're going to try doing the weekly meeting on Wednesday.
The meeting time will be:
Wednesday March 26, 19:00 UTC.
(That's 3pm EDT and
Yawning Angel wrote:
> On Mon, 17 Mar 2014 13:26:25 +0100
> Fabian Keil wrote:
>
> > My pleasure. Unfortunately I apparently missed one issue on FreeBSD
> > 8.4:
> > https://redports.org/~fk/20140317110212-48719-187908/obfsclient-0.0.1.log
>
> Ah, that's a easy fix. FreeBSD 8.x's sys/cdefs.h
Hey Noah,
It seems that you successfully compiled Stegotorus, congratulation! ;)
Although, you still have problem with compiling the unit tests in google
framework, they are not essential in solving your challenge. I recommend
that you start working on your challenge now.
Per Google's recommenda
13 matches
Mail list logo
