Delivery-Date: Mon, 01 Dec 2014 17:45:46 -0500
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=-3.9 required=5.0 tests=BAYES_00,PLING_QUERY,
	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 636001E0E4D;
	Mon,  1 Dec 2014 17:45:45 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0917530662;
	Mon,  1 Dec 2014 22:45:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 167C53064E
 for <tor-talk@lists.torproject.org>; Mon,  1 Dec 2014 22:45:38 +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 4XAfFb7JCUds for <tor-talk@lists.torproject.org>;
 Mon,  1 Dec 2014 22:45:38 +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 D02D1303B4
 for <tor-talk@lists.torproject.org>; Mon,  1 Dec 2014 22:45:37 +0000 (UTC)
Mime-Version: 1.0
Date: Mon, 01 Dec 2014 22:44:58 +0000
From: fuckyouhosting@ruggedinbox.com
To: tor-talk@lists.torproject.org
In-Reply-To: <547C1EE3.7010604@riseup.net>
References: <d44c9fb94badc9743f9491dc11db52c0@ruggedinbox.com>
 <547BD14E.3060902@gna.org>
 <ae0862eb6ac3ff7fa2798255b2676645@ruggedinbox.com>
 <547C1EE3.7010604@riseup.net>
Message-ID: <ce591bffa5f5cd607106259789f652b1@ruggedinbox.com>
X-Sender: fuckyouhosting@ruggedinbox.com
Subject: Re: [tor-talk] =?utf-8?q?=28D=29DOS_over_Tor_network_=3F_Help_!?=
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-12-01 07:55, Mirimir wrote:
> On 12/01/2014 12:13 AM, fuckyouhosting@ruggedinbox.com wrote:
>> On 2014-12-01 02:24, Christian Gagneraud wrote:
>>> On 01/12/14 14:46, fuckyouhosting@ruggedinbox.com wrote:
>>>> Hi List! We (try to) maintain a free hosting platform for hidden 
>>>> service
>>>> websites, here: http://fuckyouhotwkd3xh.onion
>>>> but recently all the hosted hidden services became unreachable.
>>> [...]
>>>> So .. question: is there a way to understand which hidden service is
>>>> causing all this ?
>>>> 
>>>> Suggestions are welcome!
>>> 
>>> This might help:
>>> https://lists.torproject.org/pipermail/tor-talk/2014-November/035787.html
>>> 
>>> Chris
>>> 
>>>> 
>>>> Thank you.
>> 
>> Hi again, ok we followed the advise and captured a number of sessions,
>> while starting Tor and while reloading it, several times to be sure.
>> 
>> We splitted and sorted the results with this command:
>> grep "PURPOSE=HS" dbg3.txt|awk '{ print $9 }'| sort |less
>> (which print just the hidden service name, for example
>> REND_QUERY=fuckyouhotwkd3xh)
>> but are unable to find an address repeated more than around 30 times,
>> example:
>> 
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> REND_QUERY=fuckyouhotwkd3xh
>> 
>> in short, the addresses are balanced among all the files, still unable
>> to find the 'black sheep'.
> 
> In your torrc, create a new test hidden service, and comment out all of
> the rest. The new hidden service should be accessible. If it's not, you
> have other problems. If the new hidden service is accessible, add back
> the old ones, one at a time, and check accessibility of the test hidden
> service after each addition. That should reveal the black sheep.

Hi, thanks for the suggestion but we were looking for a more 
'programmatic' way: a straight indication about the offending HS, which 
eventually can be used by fail2ban or a custom script
to automatically switch off the black sheeps.

Moreover, consider that we are talking about hundreds of hidden services 
..

-- 
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

