Delivery-Date: Mon, 08 Dec 2014 17:26:08 -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,URIBL_BLOCKED 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 A33761E08C2;
	Mon,  8 Dec 2014 17:26:07 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 35B2630F4F;
	Mon,  8 Dec 2014 22:26:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 7BF1830B44
 for <tor-talk@lists.torproject.org>; Mon,  8 Dec 2014 22:26:01 +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 U7UeCo7Iz4xy for <tor-talk@lists.torproject.org>;
 Mon,  8 Dec 2014 22:26:01 +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 4313D28499
 for <tor-talk@lists.torproject.org>; Mon,  8 Dec 2014 22:26:01 +0000 (UTC)
Mime-Version: 1.0
Date: Mon, 08 Dec 2014 22:25:56 +0000
From: fuckyouhosting@ruggedinbox.com
To: tor-talk@lists.torproject.org
In-Reply-To: <CAD2Ti2-vK8WrZ_DgUyNs_xMXRaPAaDvh0WZgnZAVAYZ3keyb_g@mail.gmail.com>
References: <d44c9fb94badc9743f9491dc11db52c0@ruggedinbox.com>
 <b89ce16e0c471d6df1c8a007f9a2a1fb@ruggedinbox.com>
 <54844B21.6000608@riseup.net>
 <032b1350246fee3bbf864a968a701a45@ruggedinbox.com>
 <CAD2Ti2-vK8WrZ_DgUyNs_xMXRaPAaDvh0WZgnZAVAYZ3keyb_g@mail.gmail.com>
Message-ID: <28486f317540f8fcf6fae687717c22a7@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>

Hi thanks for the input, any documentation on that ?

On 2014-12-08 22:19, grarpamp wrote:
> On Mon, Dec 8, 2014 at 5:11 PM,  <fuckyouhosting@ruggedinbox.com> 
> wrote:
>> Hi yes we agree, we think that this is the best solution, currently.
>> We'll upgrade our hardware asap, adjust the scripts to have a 
>> dedicated Tor
>> daemon for each virtual host and hopefully move on.
> 
> What you'd most likely want in that case is a single
> master tor daemon to manage the network info such
> as obtaining the consensus and for any other sort of
> meta stuff you wish it to manage, and a bunch of slaves
> that save bandwidth/cpu/ram/disk by looking to the
> master for that info.
-- 
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

