Delivery-Date: Sun, 28 Jun 2015 12:00:50 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_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 6403F1E0669;
	Sun, 28 Jun 2015 12:00:48 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1F3CF36C7A;
	Sun, 28 Jun 2015 16:00:44 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3150A36C88
 for <tor-talk@lists.torproject.org>; Sun, 28 Jun 2015 16:00:40 +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 voTtsSy6G47Y for <tor-talk@lists.torproject.org>;
 Sun, 28 Jun 2015 16:00:40 +0000 (UTC)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com
 [IPv6:2a00:1450:400c:c05::22e])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id DCB8436B23
 for <tor-talk@lists.torproject.org>; Sun, 28 Jun 2015 16:00:39 +0000 (UTC)
Received: by wiwl6 with SMTP id l6so80173103wiw.0
 for <tor-talk@lists.torproject.org>; Sun, 28 Jun 2015 09:00:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=googlemail.com; s=20120113;
 h=from:message-id:date:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=I22dW3A09p3aGAA3PqLA5UwaJHhSuigZf2WXSnbXUbk=;
 b=qqM1y8VcQVLCE+d0fGo5gUvaInP5BHMu1xhh7vCoN1LgupkGzmrzxdne0RjSBNL64M
 QDr2fD2Iufo0xHXs91vW1zo9mFgK65O0oT0aWmP9Xpo8oWx42hBlzyiOrL5SxgVRyOyt
 2wObn6l4Ehmd/LnjQhClXgVodANB/24lE6tXHZdHohi8d8Tfe5h28aUAZyDF+PonTZTU
 /bsp6fNxBsYJt4wYlN/sMgTt1SjRBnHHBVs50z2IvFnPqrxBXNEOugSD2fteyZpr2v/W
 vVgtnuE8bd7Trrkupv7FUDNECxnI06RcHFbfCEbQnwWN5Xdxu6LscY0Fo1TmsC9saUOd
 9ktA==
X-Received: by 10.180.9.111 with SMTP id y15mr14120027wia.18.1435507237114;
 Sun, 28 Jun 2015 09:00:37 -0700 (PDT)
Received: from [172.16.41.91] (195-154-136-40.rev.poneytelecom.eu.
 [195.154.136.40])
 by mx.google.com with ESMTPSA id l6sm7925185wib.18.2015.06.28.09.00.35
 for <tor-talk@lists.torproject.org>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Sun, 28 Jun 2015 09:00:35 -0700 (PDT)
From: aka <akademiker1@googlemail.com>
X-Google-Original-From: aka <akademiker1@gmail.com>
Message-ID: <559019F3.6080206@gmail.com>
Date: Sun, 28 Jun 2015 17:59:47 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <CAJwFvsUhDbo60X9MrXRe-iKpbU4zz-8Q7W9er-+G2yk_DDS+fA@mail.gmail.com>
 <20150626202807.GK7957@moria.seul.org>
 <CAJwFvsWYZ07e68J_0Jv_vNM05FG7biQKQo64eUrB7nuj6zfWvQ@mail.gmail.com>
In-Reply-To: <CAJwFvsWYZ07e68J_0Jv_vNM05FG7biQKQo64eUrB7nuj6zfWvQ@mail.gmail.com>
Subject: Re: [tor-talk] Clear net and Tor site on the same server
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>

Hidden service is heavy on CPU, for every single TCP connection your Tor
client needs to create a new tunnel which requires quite a few RSA
calculations and those are very CPU demanding. 20 simultaneous
connections will bring your small VPS to its knees (I assume its a VPS
because of that low memory size), but 40MB RAM should be enough for that.
Oh and if your server is a raspberry pi, forget about it, first
generation rp can't encrypt more than 500KByte/s AES stream with its
tiny ARM core anyway.

Tyler Hardin wrote:
> Oops. Server = hidden service and node = relay. It made sense in my mind,
> but precision is important. I'm already kinda tight on my bitcoin node
> (190/256MB). Averaging 1MByte/s and 20 simultaneous connections, would it
> be worth trying to squeeze a Tor hidden service in there? What are the
> determinants of the memory use? Is it more # of connections or rate of
> traffic?
> 
> On Fri, Jun 26, 2015 at 4:28 PM, Roger Dingledine <arma@mit.edu> wrote:
> 
>> On Fri, Jun 26, 2015 at 04:17:37PM -0400, Tyler Hardin wrote:
>>> Why is it suggested not to do this? Does it matter as long as I'm not at
>>> all concerned about privacy? I want to run a wallet-less bitcoin node and
>>> thought I might as well make it accessible via Tor, however it definitely
>>> isn't worth paying for an extra server to serve as a dedicated proxy.
>>
>> Right, I think it is fine to run a normal website on the Internet and also
>> make it available as an onion site by running Tor on the same computer.
>>
>> It all comes down to what security goals you have in mind. If one of
>> your goals is to protect the location of the website so people visiting
>> it cannot learn where it is, then you have many more things you ought
>> to think about.
>>
>> But for your situation, it sounds fine. For background you might enjoy:
>> https://blog.torproject.org/blog/facebook-hidden-services-and-https-certs
>> https://lists.torproject.org/pipermail/tor-talk/2015-May/thread.html#37820
>>
>>> BTW, what kind of memory usage can I get by with to run a Tor server? How
>>> about a Tor node?
>>
>> These phrases "Tor server" and "Tor node" are ambiguous. You might enjoy
>>
>> https://www.torproject.org/docs/faq#ConfigureRelayOrBridge
>> https://www.torproject.org/docs/faq#ExitPolicies
>> https://www.torproject.org/docs/hidden-services
>>
>> Running a Tor relay can use quite a bit of memory depending on how much
>> traffic it's handling. Running a Tor bridge generally means you're
>> handling much less traffic, and so the memory footprint is much lower.
>> And running an onion service (aka hidden service) is usually very low
>> memory footprint too, but it depends how popular the service is.
>>
>> Hope that helps,
>> --Roger
>>
>> --
>> 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
>>
-- 
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

