Delivery-Date: Sat, 30 Aug 2014 10:16:05 -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_SIGNED,
	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 3C6A41E08C8;
	Sat, 30 Aug 2014 10:16:04 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9371C30C62;
	Sat, 30 Aug 2014 14:15:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 88A5130C03
 for <tor-talk@lists.torproject.org>; Sat, 30 Aug 2014 14:15:56 +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 iw3WujvIAaLR for <tor-talk@lists.torproject.org>;
 Sat, 30 Aug 2014 14:15:56 +0000 (UTC)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com
 [IPv6:2607:f8b0:4001:c05::22c])
 (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 69A2D3025A
 for <tor-talk@lists.torproject.org>; Sat, 30 Aug 2014 14:15:56 +0000 (UTC)
Received: by mail-ig0-f172.google.com with SMTP id h15so10928976igd.17
 for <tor-talk@lists.torproject.org>; Sat, 30 Aug 2014 07:15:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=cyblings.on.ca; s=google;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=gMf8kTRfQ+5AGkoWcG4WepQRUCjqddUGPzsTr/hJ8qY=;
 b=egoAedILozy2Yok55qPsZaQZskijqFqfaM7zXsRv21FeiYi5lJmmtLmcQict2mymVI
 BbTFRQFqFHBho/PzrPAmhiENeTNUgkB0OW/u3UHAiA7e8bajE3Xc820eMLPSaOOu7l4Y
 cz1YrbAbGYM+s0VubX9/q67FaC/HgDe9V+1ZQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
 :subject:references:in-reply-to:content-type
 :content-transfer-encoding;
 bh=gMf8kTRfQ+5AGkoWcG4WepQRUCjqddUGPzsTr/hJ8qY=;
 b=mA2GlJgd9YSxqQqGbYbrCK4HUZjD4m29CPwBzcm9+VV6GLyMhXrPiCWzIaIwoDpiDd
 2u3hEDpsRN/eJ9RUKDGQxpynhqx2hhwtia/iVmfJfNgVYaTttIy0QRgi3FARAmmJGT8o
 Y+2UHVtlqMcoBH4Bgcrg7vG61MihXlYRYTYn9ZwZX0APA0ekTcs7jXtD/rJyqsvf4PPo
 uocZBGfJL2rKpgsoQBEZroGzizpYPXIulLCtpI/1XwUoc/8/JsV13tERkszJ7G/Kdzlo
 Rq+K/0sL23i00v9OqxVQjMcjv5OT7EbPeA7mi0hrAMtJw7hVTVZXHr4+Z23G7adli7v4
 oJ2A==
X-Gm-Message-State: ALoCoQl+Jzmv4LhHzgNVLtKb4FkXizrbCTzg/3oVekpvqG7sqFyiApd7fLsz6tdKF5BxGi0XIzYx
X-Received: by 10.43.107.68 with SMTP id dx4mr1205415icc.34.1409408154148;
 Sat, 30 Aug 2014 07:15:54 -0700 (PDT)
Received: from [192.168.1.2] (69-196-152-198.dsl.teksavvy.com.
 [69.196.152.198])
 by mx.google.com with ESMTPSA id hb9sm8170662igb.17.2014.08.30.07.15.52
 for <tor-talk@lists.torproject.org>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Sat, 30 Aug 2014 07:15:53 -0700 (PDT)
Message-ID: <5401DC97.6030506@cyblings.on.ca>
Date: Sat, 30 Aug 2014 10:15:51 -0400
From: krishna e bera <keb@cyblings.on.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <53FAA2EC.6080006@riseup.net> <53FBB25F.7060804@cpunk.us>
 <5401B62E.9000604@whonix.org>
In-Reply-To: <5401B62E.9000604@whonix.org>
Subject: Re: [tor-talk] BBC: NSA and GCHQ agents 'leak Tor bugs',
 alleges developer
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>

On 14-08-30 07:31 AM, Patrick Schleizer wrote:
> Cypher:
>> On 08/24/2014 09:43 PM, Michael Wolf wrote:
>> The article was very interesting - except the part about 'here's how you
>> might want to fix this'. I certainly hope that the Tor project /is not/
>> accepting patches submitted by NSA or GCHQ! Sure, I realize those
>> agencies could very easily embed someone within the project (in fact,
>> don't a few of the Tor project folks work in intel?) but developing a
>> trusting relationship by accepting patches just seems like a bad idea to me.
> 
> How would they know the patches are made by someone paid by NSA or GCHQ?
> If they reject patches with the reason "made by NSA or GCHQ", I would
> assume that they will create a number of fake identities [if they don't
> already have them in abundance] and submit patches using fake identities
> by then.

There are several pseudonymous development sponsors (named only by
single letters).  Any of them could be GCHQ or NSA or one of their front
agencies.
It doesnt matter - all of the code remains open source and the
developers have their own public reputation to maintain.

It is counter-productuve to complain about contributors' backgrounds.
Instead, concerned people could put efforts into forming an independent,
funded group to audit the code and find/fix problems.  Everything i've
heard from Tor Project indicates to me they would welcome that sort of
contribution.

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

