Delivery-Date: Fri, 08 Aug 2014 22:46:24 -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 CF14E1E0A87;
	Fri,  8 Aug 2014 22:46:22 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C69A721528;
	Sat,  9 Aug 2014 02:46:18 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 84ACD2152C
 for <tor-talk@lists.torproject.org>; Sat,  9 Aug 2014 02:46:14 +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 chAFUIMyOhpO for <tor-talk@lists.torproject.org>;
 Sat,  9 Aug 2014 02:46:14 +0000 (UTC)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com
 [IPv6:2607:f8b0:400d:c00::236])
 (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 5846321420
 for <tor-talk@lists.torproject.org>; Sat,  9 Aug 2014 02:46:14 +0000 (UTC)
Received: by mail-qa0-f54.google.com with SMTP id k15so6430921qaq.13
 for <tor-talk@lists.torproject.org>; Fri, 08 Aug 2014 19:46:11 -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=+KtJYy+CgksT4GnPeHdHKL9Xl0FVaxud91oo6I/Nv7c=;
 b=zrgqP8DlO+g7snXlBG3vBffqBMyMFndKvCy5F+zFahLBO16r4pDRJ8gs5T40zUNhKB
 tJ1pxPh50lZVan9R73B24k+8KQZcBT9Ojc4EpuDajIjPY++aFTH9iX4BUtHD6riV7Ins
 otLKpJlkLrUh19JoKp1Taye5oiPOR0LPcDdmU95CoW1uvVJ4lOUvdYRPtdg+oOOO2Uw0
 Syr71nwYnlDs2868LRWPJvJEAdmGsv+dyrb0niKoETTGVqWLoi2XDwaLtvghsl8FJm//
 aZ9VcZ+wwGRHb8ItYDs0u3PLeGCk9SDUJrr4MzQR1wUG7G3AlNTWIRs22tfjGV4OuE8U
 OcHg==
MIME-Version: 1.0
X-Received: by 10.229.225.131 with SMTP id is3mr42813354qcb.2.1407552371868;
 Fri, 08 Aug 2014 19:46:11 -0700 (PDT)
Received: by 10.229.148.82 with HTTP; Fri, 8 Aug 2014 19:46:11 -0700 (PDT)
In-Reply-To: <bf685c8b06f43e103e1df464e4d9c400@ruggedinbox.com>
References: <bf685c8b06f43e103e1df464e4d9c400@ruggedinbox.com>
Date: Fri, 8 Aug 2014 22:46:11 -0400
Message-ID: <CAD2Ti285aRzSL_19neuK8d8HiWxRuXs5RYesWNOxT7F55oZnpA@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Three questions
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 Fri, Aug 8, 2014 at 8:38 PM,  <ml@ruggedinbox.com> wrote:
> 1. when running a service as a hidden service, for example a web server, the
> client IP address is always 127.0.0.1.
> Is there a way to have some more 'unique' information about the visitor, in
> order to mitigate a DDOS attack ?

Not really... user-agent, username/password, some tcp fingerprints, javascript,
the attack signature, etc, that is about all.

> 2. when I connect to a hidden service, as a client, for example using TBB or
> ssh, does any of the nodes in the circuit know my final destination ?

Not really... but there are some papers in the anonbib about what your
favorite gov't or last hop might be able to know.

> 3. about connecting to ssh as a hidden service: many howtos explain to edit
> ~/.ssh/config and add a 'ProxyCommand' definition, for example this
> resource:
> http://unethicalblogger.com/2012/06/13/ssh-as-a-hidden-service.html
> but we found that also torsocks (for example: torsocks ssh
> root@s4bysmmsnraf7eut.onion) works well.

Break yourself of the habit of logging in as root and use ssh keys.

> We did some (simple) packet sniffing and analysis and weren't able to find
> any leak.
> We prefer using torsocks because if you forget to add the ProxyCommand
> definition (thus trying to directly connect to the onion address), the onion
> address may be DNS leaked.
>
> What do you think about using torsocks to connect to ssh as a hidden service
> ?

Unless the proxy app is broken there is no leak, that is easily testable.
I suggest it is more configurable and maybe even more reliable to use
proxycommand which is a common application pipe, than torsocks which
is a library overlay hack.

> Thank you very much for your attention and sorry again if wrong list,

Thanks for bringing another mail service into the world, it is needed.
-- 
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

