Delivery-Date: Sat, 23 May 2015 05:00:37 -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 D03AD1E0457
	for <archiver@seul.org>; Sat, 23 May 2015 05:00:33 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E8E1C3560C;
	Sat, 23 May 2015 09:00:28 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 6BD2535608
 for <tor-talk@lists.torproject.org>; Sat, 23 May 2015 09:00:25 +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 N_vgvVvP0h2c for <tor-talk@lists.torproject.org>;
 Sat, 23 May 2015 09:00:25 +0000 (UTC)
Received: from mail-yh0-x22e.google.com (mail-yh0-x22e.google.com
 [IPv6:2607:f8b0:4002:c01::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 47FE1355AF
 for <tor-talk@lists.torproject.org>; Sat, 23 May 2015 09:00:25 +0000 (UTC)
Received: by yhrr66 with SMTP id r66so10171146yhr.3
 for <tor-talk@lists.torproject.org>; Sat, 23 May 2015 02:00:23 -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=ADuCZ0rqga3aq/X7qf6mBl7q6Y1A0YgBYYC8KiavTzw=;
 b=xDojc0ne6EwUKgGkGldAULTmQKuA6zM+B+Pa73ZzqUPPTosPabaCr3uTNOS+HuZMcK
 47YsFnbKJ6Z4e9tZchVtdHfeNA+kMZVh5BZ8sJLn2EzWZ3rvFBXQCD3WI+1N64n/jg33
 K5PMo5JD2cABop1Nk7D/IHuPHgYslWzWYPmxLT3VntD6yZIPg5yQvCQtSYBGnRQ+w0DA
 5WiITsu5MnYYfzg3mh83/JVceOMZvhZ6zknxlG2QnskOWn+LwsbN+DT/GFFteugXN2d0
 FqDNiv4mcEEd+XS9EvROcOXi01v7AX+duRCdlXZWms6DujyNYm/55RpkbaUYCx6tmLhR
 speQ==
MIME-Version: 1.0
X-Received: by 10.236.209.42 with SMTP id r30mr12197755yho.5.1432371622870;
 Sat, 23 May 2015 02:00:22 -0700 (PDT)
Received: by 10.129.35.7 with HTTP; Sat, 23 May 2015 02:00:22 -0700 (PDT)
In-Reply-To: <5537F142.7030002@sonsorol.org>
References: <CAFN1edqPWLSm-Ru6ZcQwa741YPqXtDOQBZxBnYVmruRhN4NxuA@mail.gmail.com>
 <5537F142.7030002@sonsorol.org>
Date: Sat, 23 May 2015 02:00:22 -0700
Message-ID: <CAFN1edqSq0dZ9zkq3vJK=wKzsrZZQSxLq69ctqDNOW1-+D0J-Q@mail.gmail.com>
From: David Stainton <dstainton415@gmail.com>
To: tor-talk@lists.torproject.org, Chris Dagdigian <dag@sonsorol.org>
Subject: Re: [tor-talk] Quantum Insert detection for everyone
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>

Hi tor-talk,
Hi Chris,

I've finally fixed all the false positive bugs in honeybadger (as far
as I know!).
I've updated the docs here with a few additional usage considerations
that Tor exit operators might find helpful:

https://honeybadger.readthedocs.org/

If a TCP attack is detected then honeybadger will write json attack
reports to the logs directory. If the CLI option
-metadata_attack_log=false is set then the attack logs will contain
base64 blobs... and so this is not a human readable format which is
why I created the honeybadgerReportTool which makes it VERY easy to
see the injected data with it's color coated hex dump diff output:

https://github.com/david415/HoneyBadger/blob/master/cmd/honeybadgerReportTool/main.go


Please feel free to write me on or off list to ask any question you
may have about how honeybadger works or how to use it.

Cheers,

David


> I run a US-based exit node and would be interested in a way to run this
> software without compromising the users exiting my node. Looking forward to
> your additional writeups - especially anything geared towards exit nodes and
> quantum insert detection.
>
> -Chris
-- 
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

