Delivery-Date: Sat, 02 Apr 2016 11:56:04 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD 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 A51781E02CA;
	Sat,  2 Apr 2016 11:56:02 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 09AB139EC2;
	Sat,  2 Apr 2016 15:55:56 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 895EA39EC2
 for <tor-talk@lists.torproject.org>; Sat,  2 Apr 2016 15:55:52 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 xim7w4gxc5D0 for <tor-talk@lists.torproject.org>;
 Sat,  2 Apr 2016 15:55:52 +0000 (UTC)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com
 [IPv6:2607:f8b0:4001:c05::231])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 6C9B739DEA
 for <tor-talk@lists.torproject.org>; Sat,  2 Apr 2016 15:55:51 +0000 (UTC)
Received: by mail-ig0-x231.google.com with SMTP id cl4so22219674igb.0
 for <tor-talk@lists.torproject.org>; Sat, 02 Apr 2016 08:55:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=bentasker.co.uk; s=google;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to;
 bh=MahGWjs6OoR7QejdVObv00QjP1vNDRqhUa+Hum2znJY=;
 b=OME//Mwb41CEmg1DWeecY+VxQjjB92GU5FecNxhaRxe9LQK7Ix92Zt8p2pzjNJ7gfI
 G5FppoAyuS/YL6/VYN8j1xq/kWSB4fpDhDnR5mdmrVHUEXWWLruSuVVR2smrogsiN9Cy
 P/vopwk/lQofL+evLSTqLE2rfUZLo64Uo2lOE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to;
 bh=MahGWjs6OoR7QejdVObv00QjP1vNDRqhUa+Hum2znJY=;
 b=baq/NJM1jJGT8cmzWMVa4sb9T/EjJnS4hj3alkiHSMs0xlTYA4PE0Ao9woRaxchnpl
 y2d2bjoEJJAG4mzwMLLaXh7u6UsYaSVIH1eLJq2y6iHTfJ0zpQkQzDNqeKkFc5wnEXEh
 kMtqY/dO/7OLG0zU6D0q50K14LWfsct8GT6h3ICcUUj1tmbsTRsKotj0qu7h40oRZmJs
 RremYugBSMjLlvvk/RRhqmURokrqex3SdWftY1/hz94MSeh5L3eK4fs/dDAShJW/Gjbb
 1mS3/PTeScHk2vggjw7UwpONuSqJzP4aJkuhD8V4koh/K2v+DQtXHH0GQWYfpS5FBmmi
 3/Aw==
X-Gm-Message-State: AD7BkJLs6RPK4pUS/jhzY5STEg+YHVdamHyOqqSZcGvO5z1QQgbAsNm8pWDl8I/F4l82pGGs+b8ifJ5hAVI0Uw==
MIME-Version: 1.0
X-Received: by 10.107.137.16 with SMTP id l16mr9437887iod.197.1459612549095;
 Sat, 02 Apr 2016 08:55:49 -0700 (PDT)
Received: by 10.64.10.132 with HTTP; Sat, 2 Apr 2016 08:55:49 -0700 (PDT)
X-Originating-IP: [2001:470:69d7:4ca::ffd6]
In-Reply-To: <b5cc236714de44496df72d17837b2de9@swift.generated>
References: <b5cc236714de44496df72d17837b2de9@swift.generated>
Date: Sat, 2 Apr 2016 16:55:49 +0100
Message-ID: <CABMkiz5xsCOsk4CsR0NvZoJNkjfNGQft+MsTW5oCoOh70krfWQ@mail.gmail.com>
From: Ben Tasker <ben@bentasker.co.uk>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Tor and child pornography
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>

> I think it's pretty clear that when someone puts on the list a complain
about a popular hidden service being attacked,
> and refuse to give any information about the identity of the hidden
service due to "legal", e.g. traffic shaping attacks
> recently, it will be a child pornography operation.

Personally, I think you're making unfair assumptions there. If someone
comes on the list and says "I can't access abc.onion" then that email
address is publicly linked as being operated by a visitor to abc.onion. It
might be that the content of abc isn't all that objectionable, but isn't
legal wherever they're viewing from, it could also be that the person
simply doesn't want to be "publicly" associated with the content, again,
despite it being legal.



> It is well known that Tor onion sites are a haven for this,

And yet the Parliamentary Technology Group recently noted in a report that
most paedophiles, in fact, do not use Tor because they find it too slow.
It's commonly stated that that kind of content exists on hidden services,
and it certainly does to some extent, but a haven? Hidden services aren't
exactly crawling with it, especially in comparison to things like Freenet.
See also the Reddit thread (sorry haven't got a link to hand) where a self
confessed child porn consumer talks about his experiences trying to find
new content on Hidden Services.

The research you refer to also had a number of concerns about methodology
and findings raised. Not least that the methodology they used would have
been positively affected if LE organisations were (as they almost certainly
do) regularly checking if known sites were still online

> Is it really appropriate to use the tor-talk list to encourage child
abuse? I do not think so.

Here, I agree with you. But I'm not sure I agree that that's what's
actually happening, at least not on a sizeable scale.

On Sat, Apr 2, 2016 at 4:15 PM, <e347c518@ghostmail.com> wrote:

> I think it's pretty clear that when someone puts on the list a complain
> about a popular hidden service being attacked, and refuse to give any
> information about the identity of the hidden service due to "legal", e.g.
> traffic shaping attacks recently, it will be a child pornography operation.
> It is well known that Tor onion sites are a haven for this, and research
> has shown a lot of hidden services use is related to these sites.
>
>
>
>
> Is it really appropriate to use the tor-talk list to encourage child
> abuse? I do not think so. Obviously there is not much that can be done
> about these immoral websites due to the nature of Tor, but as the wider
> community of users of Tor, should not specifically helping child
> pornographers fix or protect their hidden service onions.
>
>
>         Sent from secure GhostMail. Easy and free encrypted email, chat
> and cloud storage, free sign up here: https://www.ghostmail.com
>
> --
> 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
>



-- 
Ben Tasker
https://www.bentasker.co.uk
-- 
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

