Delivery-Date: Mon, 08 Dec 2014 17:19:43 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,PLING_QUERY,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,
	T_DKIM_INVALID,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 2E1101E06EF;
	Mon,  8 Dec 2014 17:19:42 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DD0C131C48;
	Mon,  8 Dec 2014 22:19:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B51B531785
 for <tor-talk@lists.torproject.org>; Mon,  8 Dec 2014 22:19:34 +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 u8cD8jwDlUGx for <tor-talk@lists.torproject.org>;
 Mon,  8 Dec 2014 22:19:34 +0000 (UTC)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com
 [IPv6:2a00:1450:400c:c05::230])
 (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 6920429171
 for <tor-talk@lists.torproject.org>; Mon,  8 Dec 2014 22:19:34 +0000 (UTC)
Received: by mail-wi0-f176.google.com with SMTP id ex7so6102752wid.3
 for <tor-talk@lists.torproject.org>; Mon, 08 Dec 2014 14:19:31 -0800 (PST)
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=yeENgu0oQf+2uoTDP1FmaTKR3ywb2hIRT/4cWKDHurg=;
 b=tSxQkvv/vkPze8ZkvfF8gUVBW1fOIAs1quTs1oyUegx4Y2VDdx+LGito8sTOBGmVzy
 OQ7t3N8ATOXHZdpa7xHIEmc7n+x4ZgZSkFIlcJcW02Eo1HxhSvHYmUHo2D1gZHW/1aj0
 hCSEGvn4McOO/z8mOyB+3CLJ8N1jdxLDWr1Y3aH0f38K/AxR57e4zswwB+8KUhQvAK4E
 8YrJ6y1hdUp2MB1GW0fkJUbrMTvysmYCxecBpygNgG4YT6KBvcTnCYJ+ZSV/G6v8jRaN
 ncyETjMzTdqFF9xXHeG6mdpJdZyrC0GvDh/4To3grlp7DWfUjXeEXZ/mqT/3UX2MPr7K
 2zbQ==
MIME-Version: 1.0
X-Received: by 10.194.62.76 with SMTP id w12mr49083099wjr.5.1418077171559;
 Mon, 08 Dec 2014 14:19:31 -0800 (PST)
Received: by 10.216.151.130 with HTTP; Mon, 8 Dec 2014 14:19:31 -0800 (PST)
In-Reply-To: <032b1350246fee3bbf864a968a701a45@ruggedinbox.com>
References: <d44c9fb94badc9743f9491dc11db52c0@ruggedinbox.com>
 <b89ce16e0c471d6df1c8a007f9a2a1fb@ruggedinbox.com>
 <54844B21.6000608@riseup.net>
 <032b1350246fee3bbf864a968a701a45@ruggedinbox.com>
Date: Mon, 8 Dec 2014 17:19:31 -0500
Message-ID: <CAD2Ti2-vK8WrZ_DgUyNs_xMXRaPAaDvh0WZgnZAVAYZ3keyb_g@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] (D)DOS over Tor network ? 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-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 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

