Delivery-Date: Fri, 26 Jun 2015 05:25:46 -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=-3.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_SIGNED,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 8A9A31E0669;
	Fri, 26 Jun 2015 05:25:44 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id ACE2736B7B;
	Fri, 26 Jun 2015 09:25:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AB74A36B27
 for <tor-talk@lists.torproject.org>; Fri, 26 Jun 2015 09:25:36 +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 vYivcwyVdw3v for <tor-talk@lists.torproject.org>;
 Fri, 26 Jun 2015 09:25:36 +0000 (UTC)
Received: from perdizione.investici.org (perdizione.investici.org
 [94.23.50.208])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.autistici.org",
 Issuer "Autistici/Inventati Certification Authority" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 7E1F536B0C
 for <tor-talk@lists.torproject.org>; Fri, 26 Jun 2015 09:25:36 +0000 (UTC)
Received: from [94.23.50.208] (perdizione [94.23.50.208]) (Authenticated
 sender: griffin@cryptolab.net) by localhost (Postfix) with ESMTPSA id
 1AE14120F21
 for <tor-talk@lists.torproject.org>; Fri, 26 Jun 2015 09:25:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptolab.net;
 s=stigmate; t=1435310704;
 bh=O/7oDq3vsdL6+r1R+Gru2fLMq9cWdRVFo9sEwDKfR7Y=;
 h=Date:From:To:Subject:In-Reply-To:References;
 b=RxV4/UqUj5fhwozKCETohxeAYRuFBTrCA6zop9k9Xuxj/WNrJua0klo05fS9xIkBo
 FHfnpzXNpwtbw7XtVmgzXG8sRC6zkKXt5sklugyQdcmsIgR70POXTVXeVhdIimy7yB
 qawAxiFzg4PONF0TreBmJkaDVFj+Z2Z6pEHZ/+S0=
MIME-Version: 1.0
Date: Fri, 26 Jun 2015 05:25:04 -0400
From: Griffin Boyce <griffin@cryptolab.net>
To: tor-talk@lists.torproject.org
In-Reply-To: <4597361435307842@web23m.yandex.ru>
References: <4597361435307842@web23m.yandex.ru>
Message-ID: <025ae710ed4b22796ea95b61b1af999e@cryptolab.net>
X-Sender: griffin@cryptolab.net
User-Agent: Roundcube Webmail
Subject: Re: [tor-talk] Creation of TOR Linux distribution for relay or
 server with everything preconfigured
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>

   Most of the configuration (at least in my case) has to do with 
deciding on the right speed for the relay and setting a bandwidth cap.  
And when using a VPS, I set "AccountingMax" and "AccountingStart" to 
stay within my expected billing range.  So I would say that would 
present the biggest issue for me with regards to having optimal settings 
for something preconfigured.

   However, you can make a relay just by configuring your torrc file (in 
/etc/tor) and then restarting tor.  Here's a basic torrc file for a 
relay:

#####
Log notice file /var/log/tor/notices.log
RunAsDaemon 1  # Run Tor in the background
DataDirectory /var/lib/tor # required
ORPort 9001 # required
Nickname relayname # Name your relay!
AccountingMax 960 GB # only pass up to 960gb...
AccountingStart month 3 15:00 # ...per month
ExitPolicy reject *:* # no exits allowed
#####

   Once you have your torrc file configured, run the command: sudo -u 
debian-tor tor.



On 2015-06-26 04:37, Ivan Pernar wrote:
> I'm Linux user and I attempted to set up TOR relay or server but I'm
> too unexperianced to do that.
> 
> I tried to youtube to learn but as much as I understand, since end of
> Vidalia, there is no simple (graphical) way to set it up.
> 
> So, as an end user I came up to a fairly simple solution that would in
> the same time remove insecurity (Windows machines as nods) and in the
> same time simplify setting up Tor reley or server.
> 
> And that is following.
> 
> Creation of TOR Linux distribution for relay or server with everything
> preconfigured
> 
> For example, i run unconfigured Ubuntu, If I want to be a reley or
> server I just go to VirtualBox, start Virtualmachine - Tor Linux
> distribution for reley or server and bring up TOR reley or server with
> a click of a mouse. I need not to configure anything becaouse
> distribution has all precofigured, I just need to make it running.
> 
> On that way (with VirtualBox), you could run Linux Tor server or reley
> even within Windows machine.
> 
> What is your view on that issue?
> Do you think it would be to complicated to create such distribution?
> 
> All the best and good luck!

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

