Delivery-Date: Sun, 14 Sep 2014 04:14: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 6E3801E0A2D;
	Sun, 14 Sep 2014 04:14:45 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9E2AF2F687;
	Sun, 14 Sep 2014 08:14:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9AD462E377
 for <tor-talk@lists.torproject.org>; Sun, 14 Sep 2014 08:14: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 iLH7vE_hvqAl for <tor-talk@lists.torproject.org>;
 Sun, 14 Sep 2014 08:14:37 +0000 (UTC)
Received: from mail-wg0-x241.google.com (mail-wg0-x241.google.com
 [IPv6:2a00:1450:400c:c00::241])
 (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 58CC32ADC9
 for <tor-talk@lists.torproject.org>; Sun, 14 Sep 2014 08:14:37 +0000 (UTC)
Received: by mail-wg0-f65.google.com with SMTP id m15so939104wgh.4
 for <tor-talk@lists.torproject.org>; Sun, 14 Sep 2014 01:14:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=googlemail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=YeLwCWNMpRUEm17AowyJc7D+WRnIAakNWoN5s6meXmo=;
 b=tZIa4PamK3ktHfL6WHAbLGWQnIZGYKuByxQH+qvsb15oYLQx/+kLYRU7HVtGlcFvAs
 lX3VE5Klu/i6+Do4hRAltE6JEcCuBdNX+/ljHvytO+Gyjv+Rp/2CWQ7MyEW1Knzt2uEj
 AKg5aUfErlsxaqfDxHuPU6pJwqxna8+8JsvDMajRVcqRXzUd2gizIaS/wuaJpHu2S1wb
 iRayUKwaWyS8FYQ+szQ4Y9f8VppCPpAwU8VVt3uHNALdDAqZfLvGp6QB5ynxLkE77T1E
 6SVcZ7iUQo2c1cd/L4fSZkQeBmowkOS9g6UK1kMZp7LTGALuB7E4izoyZDZcAcLAb/Ql
 lYQA==
X-Received: by 10.194.205.196 with SMTP id li4mr24024144wjc.46.1410682474312; 
 Sun, 14 Sep 2014 01:14:34 -0700 (PDT)
Received: from [192.168.2.129]
 (dslb-188-100-168-236.188.100.pools.vodafone-ip.de. [188.100.168.236])
 by mx.google.com with ESMTPSA id c7sm7329906wib.12.2014.09.14.01.14.32
 for <tor-talk@lists.torproject.org>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Sun, 14 Sep 2014 01:14:33 -0700 (PDT)
Message-ID: <54154E65.4050001@googlemail.com>
Date: Sun, 14 Sep 2014 10:14:29 +0200
From: "Sebastian G. <bastik.tor>" <bastik.tor@googlemail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <5414C6CC.9040002@virtadpt.net>
 <20140913224225.GD36318@moria.seul.org> <5414E2AC.6060808@gmail.com>
 <14038bdc4f6dbd0f46584ea7b6b0cf9d@cryptolab.net>
 <1591461410668863@web3h.yandex.ru>
 <64329c17354894afe265ab15d9a60f16@cryptolab.net>
 <6910021410675404@web12g.yandex.ru>
In-Reply-To: <6910021410675404@web12g.yandex.ru>
Subject: Re: [tor-talk] Comcast looking for Tor traffic,
 contacting customers to threaten termination of service.
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>

14.09.2014, 08:16 John Pinkman:
>> Give me a break.  These women are being exploited against their
>> will. Taking something private and exposing it to the world as a
>> whole is completely despicable.  It's unethical.  It's not
>> comparable to pornography where consenting adults agree to make
>> media and release it.
> 
> I really don't understand why you are particularly so upset with
> PinkMeth. People's information is being exploited all over, with and
> without tor. What about facebook, or gmail, or yahoo selling your
> information to advertisers?

For data belonging to users who signed up it includes their consent.
Facebook or any other company, tracking people who have not agreed to it
is violating their privacy.

> There can be very intimate info, textual
> or graphical, there. I am sure advertisers routinely get dumps with
> nudes included as parts of the customer profiles by well known
> companies under NDA.

I'm sure you can provide some evidence for that assertion.

> How is this better than PinkMeth? Is it because
> this is done in secret, and isn't obvious?

The intention of PinkMeth is different and the usecase. Whereas people
share private information among each other with each others consent on
Facebook, somebody betrays someone's trust and uploads it to PinkMeth,
without or against the explicit consent.

> It is the nature of information that it changes domain once leaked,
> and this can't be reverted. The information originator should care
> about its protection.

To me it is unreasonable to share intimate information over Facebook or
ICQ or unencrypted email, because I am aware of the fact that parties
along the wires can read it.

Nothing seems to prevent my communication parter from betraying me.


> pictures taken with the modern cell phones aren't private. They
> usually are immediately uploaded to the cloud

I'm sure you have evidence that the user can not disable cloud storage.

>, where they are stored
> unencrypted, left to sysadmins to be watched over. These companies
> don't care about your privacy much, otherwise they would have
> encrypted them.

It is unreasonable for them to encrypt stuff they would like to work
with. I agree that they are not interested in someone's privacy, if it
collides with their business.

> These women also send them to multiple random
> parties, this also makes them not private.

If we talk about sending nudes over snapchat and assume that they will
never be shared, then this assumption will crumble pretty fast. The
statement that this pictures are taken for sending them away is not true
for all cases. Couples may take pictures or videotape themselves and it
ends up on PinkMeth as the relationship falls apart.

> What is private anyway?

If someone believes in Santa Claus or is religious with the believe in
an omnipresent being... nothing.

> Once leaked, they would end up on hundreds of sites, and they can't
> be removed from everywhere. PinkMeth is only one of them.

Attempting to remove them doesn't seem to be reasonable. It just pulls
attraction to those pictures. If PinkMeth wouldn't have been in the
news, almost no one would no about it. So it is better to not talk about
BlackMath, because if no one talks about it no one will be dragged to it.

> User stupidity is also a major part of this. Stupidity just isn't
> compatible with privacy much.

It is unreasonable to assume that third-parties handle private
information reasonable. I agree that it is stupid to give them more
information as they need to.

Your medical advisor needs to know certain things, you most likely
consider private, and you can not prevent your advisor from leaking
them. Tor can't help you here. There is no technology that can do.

> John
> 

Sebastian
-- 
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

