Delivery-Date: Sun, 27 Mar 2016 14:42: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 B7F6F1E0443;
	Sun, 27 Mar 2016 14:42:57 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C797C20429;
	Sun, 27 Mar 2016 18:42:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 979A639900
 for <tor-talk@lists.torproject.org>; Sun, 27 Mar 2016 18:42: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 3aps5AgN3fOp for <tor-talk@lists.torproject.org>;
 Sun, 27 Mar 2016 18:42:46 +0000 (UTC)
Received: from mail-vk0-x241.google.com (mail-vk0-x241.google.com
 [IPv6:2607:f8b0:400c:c05::241])
 (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 76ED138E39
 for <tor-talk@lists.torproject.org>; Sun, 27 Mar 2016 18:42:45 +0000 (UTC)
Received: by mail-vk0-x241.google.com with SMTP id a62so12229318vkh.0
 for <tor-talk@lists.torproject.org>; Sun, 27 Mar 2016 11:42:45 -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;
 bh=MATOubjsv9ojQSN97H9Mh9GH8GXdubA57Qie006OKio=;
 b=J1gPXTDh+o20USIF1lOWA8XFJHxZKDTgKHeFO+CJxcIIHHpDc1qrQpsSt4q6BGeQcl
 VApY7rS6gayLEUOLg8ksImn6hZsROAICUDBh7hHN6oULG5ohGXDjbXP7KOdb7z5ymEu4
 0rx73C6xJ2xRwUBvQSERmbqzLomNf1ZZazX8xPpblYaZt2kdWYrXWmMuOGQNe9A6+jmu
 ymbcpKAtYdc+giHLhobBHtMSO6t7VcCATvM2hf+QC1kW6uXDDAItxgCxMb78fMxX6WAY
 CGjcIRQ0XTigTuiRKV3mLnRyo6P0zjDNCV0GR7TkdfzHmNFRenwZILa8YVo7GmpwzPj0
 LErg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to;
 bh=MATOubjsv9ojQSN97H9Mh9GH8GXdubA57Qie006OKio=;
 b=EoOYNPtAWy1g969yUvfchmfpHhGoX7g2m+PllLuvnmOzdLNt9S/BGFqJK5+hfj03VK
 YTBpg/4roKI11Ul3NzWhfsiQM65CWWvUbZJRT3I2+uqH2QFpCzmA5e2DZXQx/SHr9SzC
 FJH5Yw0obdPsgpKs6t/Yu13+xVf5hfhLn9fR57s8RoAim5UCgrppa3XoSU8ev8PNeEy5
 DjOkqAslWcor4MzjJZ5+ifQ0wg78dnpxlDpbGpyKin2JWO4OAv67U1GkdEHzN824ubWe
 PaCqZJ6MbrNxWWiamFsqqqWyDutdbz4IdumU66WpOUvy7U6EUZmbO4YR0HMezBlwXEwc
 9RQg==
X-Gm-Message-State: AD7BkJIIYo52e7tdnU+FuY0XGBLamiSESpzZSf2zZc2m70TAuNpIu2/irvY8EDFZJNnbP+wkSP4XO9yX7QHhLA==
MIME-Version: 1.0
X-Received: by 10.176.2.212 with SMTP id 78mr12310865uah.2.1459104163110; Sun,
 27 Mar 2016 11:42:43 -0700 (PDT)
Received: by 10.176.69.5 with HTTP; Sun, 27 Mar 2016 11:42:42 -0700 (PDT)
In-Reply-To: <20160327113536.GA18214@hansolo>
References: <20160326101405.GA8312@hansolo>
 <CAD2Ti29iUfoj+4bNdg0c+7mqPEYQmpFafJ6f1P3MiOny011Ntg@mail.gmail.com>
 <20160327113536.GA18214@hansolo>
Date: Sun, 27 Mar 2016 14:42:42 -0400
Message-ID: <CAD2Ti2_V7LiDXYhJVR23f+N-wqhF5C+p2HobwJZE0BhSzg2M3Q@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Duplicating Tor's DNS requests
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 3/27/16, parazyd <parazyd@dyne.org> wrote:
> On Sat, 26 Mar 2016, grarpamp wrote:
>> # Combine setevents circ and stream
>> https://trac.torproject.org/projects/tor/ticket/11179
>
> Pretty interesting. I'll see what I can do.
> Anyway, I would let both clear and Tor traffic out, I just wish to log
> Tor's hostname/DNS requests and it seems a tad difficult so far.

This may do it...
Log debug file foo.txt
LogMessageDomains 1

Or you could maybe printf socks5 in or/buffers.c.

Both of those are quite heavy so wouldn't help anyone else
see what they're passing through tor in the simplified way
that the new setevents function would.

Also seems like the code may reject as invalid any IDNs (cctld, fqdn)
users may be pushing into socks5, which would be a bug for those users.
-- 
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

