Delivery-Date: Tue, 14 Oct 2014 15:59:12 -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_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,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 82BFD1E00CA;
	Tue, 14 Oct 2014 15:59:03 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id D30B031133;
	Tue, 14 Oct 2014 19:58:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id DE2893075A
 for <tor-talk@lists.torproject.org>; Tue, 14 Oct 2014 19:58:55 +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 RCSMfIlNxNDx for <tor-talk@lists.torproject.org>;
 Tue, 14 Oct 2014 19:58:55 +0000 (UTC)
Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com
 [IPv6:2607:f8b0:400c:c03::234])
 (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 BA50730470
 for <tor-talk@lists.torproject.org>; Tue, 14 Oct 2014 19:58:55 +0000 (UTC)
Received: by mail-vc0-f180.google.com with SMTP id le20so8207318vcb.11
 for <tor-talk@lists.torproject.org>; Tue, 14 Oct 2014 12:58:53 -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
 :cc:content-type;
 bh=9EzVEpPWa/mR1wPXcPodK5fjJt7e/36gPRxrmJeyCX0=;
 b=x+ajD1dGQt3E5CsSVUM38NSq2WwLO5v+EOMWkIZ6P+S7LD8V72qDyCuBC2exuKuRjJ
 OoN+8I7RLsA9y/MWPlyhcz4xVR6zbkc8h4Bdc5h80WoC403SsbbPteqyVhGqkxRTs7GP
 xihtFucxoOTT6cmp5C9qoInISjDS0zsT20yv3wIerkKsM/P44hPXr6it6uv+RoFca4Sp
 6MHdaKPP3z1vBukGKqNoIYoXoN9zbI1Qiu1GZAT0iJgyeyEPAe9mEKuBC1MvIDPlK2Oi
 xbnx5gq714Kobis6uC0MswA6wEH3B6DoIdHDpoir8KX9R/4uH9rspvOzMjeT7KKc40HF
 71Bg==
MIME-Version: 1.0
X-Received: by 10.52.29.131 with SMTP id k3mr6596567vdh.2.1413316733199; Tue,
 14 Oct 2014 12:58:53 -0700 (PDT)
Received: by 10.221.64.74 with HTTP; Tue, 14 Oct 2014 12:58:53 -0700 (PDT)
In-Reply-To: <20141014114923.602cd9b3@daffy>
References: <CAD2Ti2-XYm33QVPb7zFkb5s0NcFjbDnSpn9cLLhmvLvxzp7wPQ@mail.gmail.com>
 <20141007114623.GA5321@mutt> <20141013222913.5530e09f@daffy>
 <1413239736.3972.0.camel@16bits.net>
 <20141014104018.44ce5533@daffy>
 <20141014084832.GC1220@zeromail.org>
 <20141014114923.602cd9b3@daffy>
Date: Tue, 14 Oct 2014 15:58:53 -0400
Message-ID: <CAD2Ti2-irX5zWp7iFWe5hM1FBK2B-DmZDr1V8zaRbB7Fe+CYKQ@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: msmtp-users@lists.sourceforge.net
Cc: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] [msmtp-users] Proxy support patch
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 Tue, Oct 14, 2014 at 5:49 AM, Martin Lambers <marlam@marlam.de> wrote:
> On Tue, 14 Oct 2014 10:48:32 +0200, ilf wrote:
>> The Tor Project recommends SOCKS 4a over SOCKS 5 against DNS leaks:
>> https://www.torproject.org/docs/faq#WarningsAboutSOCKSandDNSInformationLeaks

> Yes, but only if the SOCKS5 application does DNS lookups itself, which
> we do not. What we do is basically what SOCKS4a would do.

That faq needs rewritten. It's not socks that 'leaks' what is passed
to it [1], it's the app leaking dns around the socks proxy it was told
to use (except for socks4 where that is the expected app behaviour).
Though once the app does properly pass a hostname to
socks4a or socks5, the socks server should resolve it.
Note that socks4a spec can and does handle a real IP just
like socks4, socks4a is thus not just strictly for hostnames.
Tor should not be warning about receiving an IP on its socks4a or
socks5 interface since technically it's both ok and commonplace for
users to specify only an IP as their destination. Save it for debug mode.
Tor also needs to move away from legacy mention of socks4 / socks4a
in preference to socks5. Or at least instruct to try and test socks5
configurations first... socks5 is the only one to handle ipv6.

[1] Unless your socks client lib is so crappy that it tries to
resolve namelikes itself in a leaky fashion without sending
them to the socks server.
-- 
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

