Delivery-Date: Mon, 22 Jun 2015 23:56:59 -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_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,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 AD6A21E02E4;
	Mon, 22 Jun 2015 23:56:57 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B8C2C36332;
	Tue, 23 Jun 2015 03:56:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id E2F8E35EEF
 for <tor-talk@lists.torproject.org>; Tue, 23 Jun 2015 03:56:46 +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 W08DzcWbbuHA for <tor-talk@lists.torproject.org>;
 Tue, 23 Jun 2015 03:56:46 +0000 (UTC)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com
 [IPv6:2607:f8b0:4001:c03::230])
 (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 C079D35E86
 for <tor-talk@lists.torproject.org>; Tue, 23 Jun 2015 03:56:46 +0000 (UTC)
Received: by iebrt9 with SMTP id rt9so3496256ieb.2
 for <tor-talk@lists.torproject.org>; Mon, 22 Jun 2015 20:56:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=dgTG1pV6MOmmWnEzqXW399ulTAcl4Ads/hcgJ/04YwI=;
 b=YJXZ3rJvBUEWpaCm/zlAhjzB4Y1O1eI7/r+ayzE4RGgczoNeUcMvgmbLyMTwLvbIdV
 /mDg0dydqsvJQKgNS1vxIbT9Yxrd5f7Bc4m70gcMfSuPvRwdYEyrSGp1WMHL36ebH4ug
 Rkgx6rJ32wKRqgOwLmhhjvRErKy17NAv0UGMXKU8qy+wOuAp3Nyu+xC+zBns0KrSfyxP
 xw9vMlOsJYGIbCEpdW65Ytl/1mtkcpXpWsU2p86q+rQnSWNSaaiP5uN3q1PxuNrd33c3
 FxPmM0xiXKNrSIHENzknn4dds5tNxKylwhhEIltUobH95p0wpnEfsfL4VCCtKU16S/17
 St/Q==
MIME-Version: 1.0
X-Received: by 10.107.132.206 with SMTP id o75mr30799545ioi.52.1435031804519; 
 Mon, 22 Jun 2015 20:56:44 -0700 (PDT)
Received: by 10.36.107.140 with HTTP; Mon, 22 Jun 2015 20:56:44 -0700 (PDT)
In-Reply-To: <ab223f4061153c88e9e956c65c4b7f0d.squirrel@s4bysmmsnraf7eut.onion>
References: <ab223f4061153c88e9e956c65c4b7f0d.squirrel@s4bysmmsnraf7eut.onion>
Date: Mon, 22 Jun 2015 23:56:44 -0400
Message-ID: <CAD2Ti2-2MHoUhW+ZZBzRMdBnx8-_eYw1P8D_7dsjoSvE=fZd5A@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Hidden service honeypot
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 Mon, Jun 22, 2015 at 6:36 PM,  <bidet@ruggedinbox.com> wrote:
> The landing page includes some javascript that looks shady.
> ...
> I'm interested in knowing how this affects the tor browser and tails, and
> could this technique be used in other scenarios by different adversaries.

If one thinks that TBB and VM is all that is needed to protect oneself
from random driveby 0day exploits, you need to think again. The
minimum is independant routing into tor via external device. And
even that assumes tor and the device and its stack aren't breakable
or broken. Layer defences, do not use just one.
-- 
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

