Delivery-Date: Thu, 31 Mar 2016 00:53:11 -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 1E82B1E0EC3;
	Thu, 31 Mar 2016 00:53:09 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1A04339F4B;
	Thu, 31 Mar 2016 04:53:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 366E03960D
 for <tor-talk@lists.torproject.org>; Thu, 31 Mar 2016 04:53:01 +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 URbBTo5A1WqY for <tor-talk@lists.torproject.org>;
 Thu, 31 Mar 2016 04:53:01 +0000 (UTC)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com
 [IPv6:2607:f8b0:4001:c06::22e])
 (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 1D0C5376AB
 for <tor-talk@lists.torproject.org>; Thu, 31 Mar 2016 04:53:00 +0000 (UTC)
Received: by mail-io0-x22e.google.com with SMTP id q128so98980881iof.3
 for <tor-talk@lists.torproject.org>; Wed, 30 Mar 2016 21:53:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=cyblings.on.ca; s=google;
 h=subject:to:references:from:message-id:date:user-agent:mime-version
 :in-reply-to:content-transfer-encoding;
 bh=dzTR0vkpwuR9a8BQVNA3bGFoaMEeLpzCnOWWeBP1GOM=;
 b=AkHnomP4HVzSoao5Tyfd7JJrV3Gp92z6cRRvetNopY7XFAPQQqKhB63C5h+/Wiub9N
 KXINn3urX5kQBJ8lYh1EgYwk01BJAzLAQ3ENJGtcygRv7tiRAbKvEJ8UW+JqguCYik0k
 HB5uV89TZDr/GncLvd3sZLvY4ed4wHTlTvPno=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:subject:to:references:from:message-id:date
 :user-agent:mime-version:in-reply-to:content-transfer-encoding;
 bh=dzTR0vkpwuR9a8BQVNA3bGFoaMEeLpzCnOWWeBP1GOM=;
 b=JhI431nZCA++SS0ODFwyIlwQORz80nX6tKGOcuX4VyHrA9MQzt3dj+3TZ/ciX/tbNH
 rDzszydKB5hguoWM355axJO+6rkPJHLDwoZ23ECZjrZhbRj8mbe68QoiK0zyg+GLtELX
 GXDUb4e73KgnknY5ZcakP978HABVGWaVbj9X725tTap5NpRQt8L4JGVsG96ovTuvO/oe
 GgSd3mfm+tzZD2ixixt9m/MWJzFsUsvAUljHrRsHPFtORT8jM4GFjf/MGIt0k8LfQzJx
 OPtSGe9ACGSVAVwn0dHlWvs2M5Z+SPbH6hQJqU9ibv1QhScIe3iYse/7irIh9Mfl+KC5
 8X4g==
X-Gm-Message-State: AD7BkJKx1/JudJd1GRp44koj3Ab4k4F7x3OPRLW7NiJ4ReSbuhgWIRKEh5wLPTkD0tI4Sg==
X-Received: by 10.107.128.26 with SMTP id b26mr676539iod.87.1459399978183;
 Wed, 30 Mar 2016 21:52:58 -0700 (PDT)
Received: from [192.168.1.2] (69-196-152-198.dsl.teksavvy.com.
 [69.196.152.198])
 by smtp.googlemail.com with ESMTPSA id j7sm2657403igv.22.2016.03.30.21.52.56
 for <tor-talk@lists.torproject.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Wed, 30 Mar 2016 21:52:57 -0700 (PDT)
To: tor-talk@lists.torproject.org
References: <F4A8F992-2FBE-4B7D-A20D-C5D00F87C8C5@nrl.navy.mil>
From: krishna e bera <keb@cyblings.on.ca>
X-Enigmail-Draft-Status: N1110
Message-ID: <56FCAC2F.5030101@cyblings.on.ca>
Date: Thu, 31 Mar 2016 00:48:47 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <F4A8F992-2FBE-4B7D-A20D-C5D00F87C8C5@nrl.navy.mil>
Subject: [tor-talk] fwd: FBI Is Pushing Back Against Judge's Order to Reveal
 Tor Browser Exploit
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>

"In February 2015, the FBI seized a dark web child pornography site and
ran it from their own servers for 13 days. During this time, the agency
deployed a NIT against people who visited specific, child pornography
threads, which grabbed their real IP address, among other technical
details."

article at
https://motherboard.vice.com/read/fbi-is-pushing-back-against-judges-order-to-reveal-tor-browser-exploit

Do we know what that exploit might have been?
Of course lots of bugs have been fixed in upstream Firefox since last
year, so it wasnt necessarily a TorBrowser specific bug.  Indeed, from
online discussions, it seems many people are using kludged setups such
as stock browsers with proxy and standalone Tor.

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

