Delivery-Date: Wed, 16 Jul 2014 08:27:02 -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 90BD21E0351
	for <archiver@seul.org>; Wed, 16 Jul 2014 08:27:00 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A03FE2FAA8;
	Wed, 16 Jul 2014 12:26:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D09EA2FA6D
 for <tor-talk@lists.torproject.org>; Wed, 16 Jul 2014 12:16:18 +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 5_bvzX-AWkAu for <tor-talk@lists.torproject.org>;
 Wed, 16 Jul 2014 12:16:18 +0000 (UTC)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com
 [IPv6:2607:f8b0:400e:c02::234])
 (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 A14522F9F0
 for <tor-talk@lists.torproject.org>; Wed, 16 Jul 2014 12:16:15 +0000 (UTC)
Received: by mail-pd0-f180.google.com with SMTP id y13so1153129pdi.39
 for <tor-talk@lists.torproject.org>; Wed, 16 Jul 2014 05:16:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:from:date:message-id:subject:to:content-type;
 bh=GGndS5ZfzbmX2PX+uoCRJGlzajvoxN4OlZWtJBwR13A=;
 b=bRorrfzMINOiRalALOwwPKU/Bk+d1cCoIzuq2TsL5NJ5n8B1pPFdiHzoZ2gjTwJ8ca
 vrAoRz4a7SiGSE2GYoEqZPREl/TBmIt6Cjmn5BNRFbtDEJxxjaRLhm3pQ6DDFUOGMK0d
 K0B+63vh35XIjIYUjgSK9QHGLn/yHFeWTsRCtEWmUNgcZFCN2mb+EKqz9qFetnXbInSK
 8wdAdc+u8ZvVc8iOODcdVKE/0F0MtNB5BuJYZiWHd/pe0GG2hXGpZ4WSdPQm4Zywq4xN
 qoz45ayvOrgkLe0VC+T5BhI+nANHq81chRBDsvHIK1CKe4D0mlITlJkHvunCWtIAgAfm
 sOAw==
X-Received: by 10.66.246.229 with SMTP id xz5mr15463348pac.119.1405512973119; 
 Wed, 16 Jul 2014 05:16:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.70.72.231 with HTTP; Wed, 16 Jul 2014 05:15:32 -0700 (PDT)
From: Fosforo <fosforo@gmail.com>
Date: Wed, 16 Jul 2014 09:15:32 -0300
Message-ID: <CAH8ZuZqbovDWFz2ngeHOb0TZyEAwbhiuoPmKFJBUVSmGib7tyQ@mail.gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] Escalating hidden services
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>

I am a big fan of pinkmeth hidden service ( hxxp://pinkmethuylnenlz.onion/ )

But it constantly times out.

As an unix administrator, I was thinking in ways to escalate such good
public services through normal clusters, and would like opinions if my
approach is valid, to suggest it to the unknown author:

1) Frontend - Only 1 node. Entry point as normal "semi-hidden" hidden
service with 32 guards (exposed, semi-hidden)
2) Backend - X number of nodes  (escaling is here) numbers of backend
hidden services with 3 guards

1) is just a relay box, nginx with reverse connection to backend hidden
services, in a different structure than backends. round robin. 32 guards to
handle good speed and lots of circuits. anonymity is not a requirement
here. each backend hidden service is a local port in 127.0.0.1 made with
torified netcat (I think there are better approaches than netcat, would
like to know )

2) apache+mysql each node, gfs filesystem (for static files) shared among
nodes, replicated mysql database.

I see latency as a problem here [ user -> nginx (hidden) -> apache (hidden)
], but I dont see more timeouts. thoughts?

--
[]s Fosforo
-------------------------------------------------------------
"Se eu tiver oito horas pra cortar uma arvore, passarei seis afiando meu
machado."
-Abraham Lincoln
-------------------------------------------------------------
-- 
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

