Delivery-Date: Mon, 11 Aug 2014 13:01:57 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 168311E0B55;
	Mon, 11 Aug 2014 13:01:56 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 43329307D5;
	Mon, 11 Aug 2014 17:01:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 6D828307D3
 for <tor-talk@lists.torproject.org>; Mon, 11 Aug 2014 17:01:50 +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 MRNel9iHh4Dh for <tor-talk@lists.torproject.org>;
 Mon, 11 Aug 2014 17:01:50 +0000 (UTC)
Received: from ruggedinbox.com (ruggedinbox.com [94.156.77.238])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 35F8026FD8
 for <tor-talk@lists.torproject.org>; Mon, 11 Aug 2014 17:01:50 +0000 (UTC)
Mime-Version: 1.0
Date: Mon, 11 Aug 2014 17:01:14 +0000
From: ml@ruggedinbox.com
To: tor-talk@lists.torproject.org
In-Reply-To: <20140809082459.GB1443@loar>
References: <bf685c8b06f43e103e1df464e4d9c400@ruggedinbox.com>
 <20140809082459.GB1443@loar>
Message-ID: <6e1b39a6a3133a116e3c2d90dfce15b3@ruggedinbox.com>
X-Sender: ml@ruggedinbox.com
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 2014-08-09 08:24, Lunar wrote:

> ml@ruggedinbox.com:
> 
>> 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 ?
> 
> See "Client identification in hidden service applications" in the April
> 2nd 2014 issue of Tor Weekly News:
> https://lists.torproject.org/pipermail/tor-news/2014-April/000039.html 
> [1]
> 
> I don't remember seeing any progress toward merging a patch answering
> Nick's comments.
> 
> 
> Links:
> ------
> [1] 
> https://lists.torproject.org/pipermail/tor-news/2014-April/000039.html



Thanks Lunar and grarpamp for your time and feedback.

Thanks for the link, also (re)read this one: 
https://blog.torproject.org/blog/hidden-services-need-some-love
and wonder how still actual it is.


About connecting to an ssh server with keys, just a little doubt: if I 
connect to all my servers without changing my ssh private and public 
keys (so without deleting '/etc/ssh' and re-creating the keys every 
time), would an attacker be able to observe that the same client (my pc) 
is connecting to those different servers ?
In short .. can my ssh client be tracker / fingerprinted if I use always 
the same public and private keys ?


Thank you very much for supporting and for your wisdom!!
RuggedInbox team
-- 
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

