Delivery-Date: Sun, 05 Oct 2014 06:46:46 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 211F81E069B;
	Sun,  5 Oct 2014 06:46:44 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id CAE7821FE9;
	Sun,  5 Oct 2014 10:46:40 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4123820DBD
 for <tor-talk@lists.torproject.org>; Sun,  5 Oct 2014 10:46:37 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 3-dlAqj1kvk2 for <tor-talk@lists.torproject.org>;
 Sun,  5 Oct 2014 10:46:36 +0000 (UTC)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com
 [IPv6:2607:f8b0:4003:c01::236])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 7D43C28517
 for <tor-talk@lists.torproject.org>; Sun,  5 Oct 2014 10:46:36 +0000 (UTC)
Received: by mail-ob0-f182.google.com with SMTP id uy5so2769255obc.27
 for <tor-talk@lists.torproject.org>; Sun, 05 Oct 2014 03:46:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=QLhA69bVzh539sAf/uivtpr6EjD1dJoMQQoEzr3xPXg=;
 b=JH7+spCQAp+CFYhKD8dAEcmVgddQDXUA0HIl61nBu2Q4qFwPbd96hF/+nf8NW54Ffh
 MfjYrdsxIKVEW/cNh68fU3sSBu+x849mlqBw2YIP8rE9qfbau9i1tK3KWRV9o6+N4sQ9
 JoL0wcR1Z8Chzw7p8hyxK93BK284yX38GbefxU5Gx9E/SiURbONKbA/k+Q+zzwbK7CzC
 uQSGs4w0LyXLjilT+Rivh8TGRQaD/jvh7yjWNbf7b2TWV3WoUcwLnRAh0V9ue6i3vhXy
 UT6ANVZ1WaoAgvnqtfUoayH1qevakreh4wqtqTI81ZOkNnneriv2gkfo4/RQactLmnJN
 whAw==
MIME-Version: 1.0
X-Received: by 10.60.94.208 with SMTP id de16mr19698152oeb.0.1412505994071;
 Sun, 05 Oct 2014 03:46:34 -0700 (PDT)
Received: by 10.202.65.85 with HTTP; Sun, 5 Oct 2014 03:46:34 -0700 (PDT)
Received: by 10.202.65.85 with HTTP; Sun, 5 Oct 2014 03:46:34 -0700 (PDT)
Date: Sun, 5 Oct 2014 04:46:34 -0600
Message-ID: <CAM+RCEg_xRY8uQfEzKtwN2d5sk5bCXnYWyxvcNPPb2wSkb+mNg@mail.gmail.com>
From: Jan Nielsen <jan.nielsen135@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] tor browser speed.
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Your home connection is not the bottleneck when it comes to tor.

Consider running a middle node!
On Oct 5, 2014 3:08 AM, <tor-talk-request@lists.torproject.org> wrote:

> Send tor-talk mailing list submissions to
>         tor-talk@lists.torproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
> or, via email, send a message with subject or body 'help' to
>         tor-talk-request@lists.torproject.org
>
> You can reach the person managing the list at
>         tor-talk-owner@lists.torproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of tor-talk digest..."
>
>
> Today's Topics:
>
>    1. Re: orWall 1.0.0 released! (Mike Perry)
>    2. bbc horizons fairly recent Re:  Tor in the media (stn)
>    3. Tech Report on Tor Growth [pdf] (Virgil Griffith)
>    4. Re: Tech Report on Tor Growth [pdf] (stn)
>    5. Re: Tech Report on Tor Growth [pdf] (Mirimir)
>    6. Re: Tech Report on Tor Growth [pdf] (Virgil Griffith)
>    7. Re: Tor Browser default window size (Hartmut Haase)
>    8. Tor Browser speed (Hartmut Haase)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 4 Oct 2014 15:27:12 -0700
> From: Mike Perry <mikeperry@torproject.org>
> To: tor-talk@lists.torproject.org
> Subject: Re: [tor-talk] orWall 1.0.0 released!
> Message-ID: <20141004222712.GG9509@torproject.org>
> Content-Type: text/plain; charset="utf-8"
>
> CJ:
> > On 04/10/14 00:27, Mike Perry wrote:
> > > Also looking forward to the "Logs" window doing something :)
> >
> > Same for me. This part will be complicated due to different kernel
> > capabilities:
> > some supports LOG target, other NFLOG, and the latter doesn't provide
> > any nflog reader in the ROM (heya, Cyanogenmod, you're brain-dead on
> this!).
> > Thus it means:
> > - detecting which kind of log is supported
> > - create some UI in order to activate logs (already have some ideas)
> > - inject some binary in the system for nflog support
> > - ? and many other things.
>
> Yeah, sounds messy. Though from the droidwall days, I thought that LOG +
> dmesg was the common denominator, but I've been running Cyanogenmod for
> a long time...
>
> > Maybe this can be avoided, as AFWall+ is considering providing some
> > intents as API end-points. This would mean:
> > - install orWall
> > - install AFWall+
> > and you'll get the best of both worlds, as AFWall will take care of the
> > iptables and log interfaces, just executing orWall orders?
>
> Hrmm. Let's hope that AFWall is being careful with this.
>
> I get nervous when I hear that root apps are going to start exposing
> APIs and Intents to configure stuff at the request of other apps.
>
> This is especially risky when we're talking about stuff like iptables
> commands that are destined for shell/direct execution. There's just too
> many ways to mess that up and open up potentially remote exploitable
> root holes (which even webpages can sometimes exploit in the case of
> Intents).
>
> --
> Mike Perry
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 801 bytes
> Desc: Digital signature
> URL: <
> http://lists.torproject.org/pipermail/tor-talk/attachments/20141004/6431787a/attachment-0001.sig
> >
>
> ------------------------------
>
> Message: 2
> Date: Sat, 4 Oct 2014 19:31:45 -0400
> From: stn <stn@ncf.ca>
> To: tor-talk@lists.torproject.org
> Subject: [tor-talk] bbc horizons fairly recent Re:  Tor in the media
> Message-ID: <BEC60FF0-84E8-41F6-8D10-1F06D46FD12A@ncf.ca>
> Content-Type: text/plain; charset=us-ascii
>
> robert pointed me back to the media archive at tor.  thanks.
>
> nice cache there.  i like how the OGV format doesn't take any time to view
> over a browser in addition to its open/free nature. other formats or
> containers include avi mov webm mp4.
>
> vlc seems to play everything so far.
>
> this video looks fairly recent ( this BBC season ) and includes another
> identifyable activist who used tor and reasonably concluded it protected
> her upon interrogation by secret police.
>
>
> https://media.torproject.org/video/BBC%20Horizon%202014-2015%20Episode%204%20-%20Inside%20the%20Dark%20Web-fTjNkbLBEqg.mp4
>
> syrian activist
> time
> about 29:55 into vid.
>
> this video looks like an attempt to gently wake people up as well as (of
> course) mentioning the  deep dark boogey net.
>
> a quick survey might categorize it the video?  ?
>
> traces networked anonymity concerns back to david chaum in early 80s.
>
> near the intro a journalist demos a smartphone on a street corner and
> about 25 wifi hosts. that's allot of redundnant signal convergence
> available for location estimation.
>
> unprotcted search concerns dealt with a pregnancy example and targetted
> marketing.
>
> etc
>
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 4 Oct 2014 16:57:03 -0700
> From: Virgil Griffith <i@virgil.gr>
> To: "tor-talk@lists.torproject.org" <tor-talk@lists.torproject.org>
> Subject: [tor-talk] Tech Report on Tor Growth [pdf]
> Message-ID:
>         <
> CADop2NHk_UF63BPFKBTO4KyE6inMn2GcTq9RO6errvjZmQ1OrA@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> I hereby submit the following PDF as a Tor Tech Report.
>
> http://dl.dropbox.com/u/3308162/tor%20growth.pdf
>
> I'll be providing the various raw data files to github/torproject shortly.
>
> Qualitative conclusions are the same.  The methodology is more
> rigorous than it was before, some quantitative differences.  Most
> notably:
> * Lots of stuff in Tor increases exponentially.
> * Absolute Torperf is increasingly nicely.
> * Normalized Torperf (Torperf relative to non-tor speeds) increases
> glacially.
> * There's statistical evidence that an injection of advertised
> bandwidth would reliably improve Torperf performance.
>
> For non-policy makers, I think the main contribution I am offering is
> a list of the various Tor growth rates (page 4, table 2)
>
> -V
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 4 Oct 2014 20:22:13 -0400
> From: stn <stn@ncf.ca>
> To: tor-talk@lists.torproject.org
> Subject: Re: [tor-talk] Tech Report on Tor Growth [pdf]
> Message-ID: <F768807D-0AB1-4AFE-A923-7F9CE206F973@ncf.ca>
> Content-Type: text/plain; charset=us-ascii
>
> thanks so much virgil.
> both report and posting dataset.
>
> steve
>
> On Oct 4, 2014, at 7:57 PM, Virgil Griffith wrote:
>
> > http://dl.dropbox.com/u/3308162/tor%20growth.pdf
>
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 04 Oct 2014 21:53:39 -0600
> From: Mirimir <mirimir@riseup.net>
> To: tor-talk@lists.torproject.org
> Subject: Re: [tor-talk] Tech Report on Tor Growth [pdf]
> Message-ID: <5430C0C3.4000805@riseup.net>
> Content-Type: text/plain; charset=windows-1252
>
> On 10/04/2014 05:57 PM, Virgil Griffith wrote:
> > I hereby submit the following PDF as a Tor Tech Report.
> >
> > http://dl.dropbox.com/u/3308162/tor%20growth.pdf
> >
> > I'll be providing the various raw data files to github/torproject
> shortly.
> >
> > Qualitative conclusions are the same.  The methodology is more
> > rigorous than it was before, some quantitative differences.  Most
> > notably:
> > * Lots of stuff in Tor increases exponentially.
> > * Absolute Torperf is increasingly nicely.
> > * Normalized Torperf (Torperf relative to non-tor speeds) increases
> glacially.
> > * There's statistical evidence that an injection of advertised
> > bandwidth would reliably improve Torperf performance.
> >
> > For non-policy makers, I think the main contribution I am offering is
> > a list of the various Tor growth rates (page 4, table 2)
>
> I've noticed something relevant to current discussion about Tor use.
>
> | Figure 8: Network Utilization Ratio (NUR) falls into three distinct
> | stages. Within each stage the fitted line is essentially flat. What
> | happened on 2013-10-08 and 2014-06-06!? The only thing we see is
> | that on 2014-06-05 (one day prior) the EFF began their Tor Challenge.
>
> Silk Road was taken down by the FBI on 2014-10-02.[0] The site still
> loaded, however, showing a "This Hidden Site Has Been Seized" message.
> And so it probably took a few days for most users to get the news.
>
> Also, contemplating Figure 8, there may be a discontinuity at about July
> 2013, when they took down Freedom Hosting.[1]
>
> I'm not aware of anything major in May-June of this year.
>
> [0]
> https://lists.torproject.org/pipermail/tor-talk/2013-October/030268.html
> [1] http://www.wired.com/2013/09/freedom-hosting-fbi/
>
>
> ------------------------------
>
> Message: 6
> Date: Sat, 4 Oct 2014 21:22:18 -0700
> From: Virgil Griffith <i@virgil.gr>
> To: "tor-talk@lists.torproject.org" <tor-talk@lists.torproject.org>
> Subject: Re: [tor-talk] Tech Report on Tor Growth [pdf]
> Message-ID:
>         <
> CADop2NHUAcOdKGK88JcbQRSspALfTfU0CjxZEv7yeswBgmnWeg@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> I will look at the "read bandwidth" data to see whether these sites going
> down was the primary cause.  But first impression it looks like that on
> those dates "read bandwidth" went down as well as "advertised bandwidth"
> went up.
>
> -V
>
> On Saturday, October 4, 2014, Mirimir <mirimir@riseup.net> wrote:
>
> > On 10/04/2014 05:57 PM, Virgil Griffith wrote:
> > > I hereby submit the following PDF as a Tor Tech Report.
> > >
> > > http://dl.dropbox.com/u/3308162/tor%20growth.pdf
> > >
> > > I'll be providing the various raw data files to github/torproject
> > shortly.
> > >
> > > Qualitative conclusions are the same.  The methodology is more
> > > rigorous than it was before, some quantitative differences.  Most
> > > notably:
> > > * Lots of stuff in Tor increases exponentially.
> > > * Absolute Torperf is increasingly nicely.
> > > * Normalized Torperf (Torperf relative to non-tor speeds) increases
> > glacially.
> > > * There's statistical evidence that an injection of advertised
> > > bandwidth would reliably improve Torperf performance.
> > >
> > > For non-policy makers, I think the main contribution I am offering is
> > > a list of the various Tor growth rates (page 4, table 2)
> >
> > I've noticed something relevant to current discussion about Tor use.
> >
> > | Figure 8: Network Utilization Ratio (NUR) falls into three distinct
> > | stages. Within each stage the fitted line is essentially flat. What
> > | happened on 2013-10-08 and 2014-06-06!? The only thing we see is
> > | that on 2014-06-05 (one day prior) the EFF began their Tor Challenge.
> >
> > Silk Road was taken down by the FBI on 2014-10-02.[0] The site still
> > loaded, however, showing a "This Hidden Site Has Been Seized" message.
> > And so it probably took a few days for most users to get the news.
> >
> > Also, contemplating Figure 8, there may be a discontinuity at about July
> > 2013, when they took down Freedom Hosting.[1]
> >
> > I'm not aware of anything major in May-June of this year.
> >
> > [0]
> > https://lists.torproject.org/pipermail/tor-talk/2013-October/030268.html
> > [1] http://www.wired.com/2013/09/freedom-hosting-fbi/
> > --
> > tor-talk mailing list - tor-talk@lists.torproject.org <javascript:;>
> > To unsubscribe or change other settings go to
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
> >
>
>
> ------------------------------
>
> Message: 7
> Date: Sun, 05 Oct 2014 11:03:23 +0200
> From: Hartmut Haase <hha4491@web.de>
> To: tor-talk@lists.torproject.org
> Subject: Re: [tor-talk] Tor Browser default window size
> Message-ID: <5431095B.8040005@web.de>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi,
> > I have learned so far that the Tor Browser does not store the used
> > window size like other programs do, becaus it always start with the same
> > size.
> at the moment Tor (3.6.6) starts with the last used window size but
> after 1 second it switches to the default size. Why?
> --
> Viele Gr??e,
> Hartmut
>
> Hungerhilfe: http://www.thehungersite.com
>
> Ohne Zensur suchen:
> http://suche.amnesty-bergedorf.de
> Googeln ohne Google:
> https://www.startpage.com/deu
>
> Das heutige Motto:
> Ein Narr tut, was er nicht lassen kann;
> ein Weiser l??t, was er nicht tun kann.
>
>
> ------------------------------
>
> Message: 8
> Date: Sun, 05 Oct 2014 11:07:54 +0200
> From: Hartmut Haase <hha4491@web.de>
> To: tor-talk@lists.torproject.org
> Subject: [tor-talk] Tor Browser speed
> Message-ID: <54310A6A.3010000@web.de>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi,
> I have upgraded my intenet connection from 25 Mbit/s to 100 Mbit/s, but
> the Tor Browser das not work faster. Why not?
> --
> Viele Gr??e,
> Hartmut
>
> Hungerhilfe: http://www.thehungersite.com
>
> Ohne Zensur suchen:
> http://suche.amnesty-bergedorf.de
> Googeln ohne Google:
> https://www.startpage.com/deu
>
> Das heutige Motto:
> Bis Du gelernt hast zu leben, ist es bereits zu sp?t.
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> tor-talk mailing list
> tor-talk@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>
>
> ------------------------------
>
> End of tor-talk Digest, Vol 45, Issue 18
> ****************************************
>
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

