Delivery-Date: Tue, 16 Sep 2014 10:52:51 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 E94191E0B00;
	Tue, 16 Sep 2014 10:52:49 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3858024123;
	Tue, 16 Sep 2014 14:52:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id BAFA522499
 for <tor-talk@lists.torproject.org>; Tue, 16 Sep 2014 14:52:43 +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 KmYHBzI4gK3x for <tor-talk@lists.torproject.org>;
 Tue, 16 Sep 2014 14:52:43 +0000 (UTC)
Received: from jessica.everdot.org (unknown [IPv6:2001:470:1f0b:1c12::1])
 (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 8FD6A22295
 for <tor-talk@lists.torproject.org>; Tue, 16 Sep 2014 14:52:43 +0000 (UTC)
Received: from mail.everdot.org (primail.everdot.org [IPv6:2001:470:dc2e:5::2])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by jessica.everdot.org (Postfix) with ESMTPS id 55200FA04B1
 for <tor-talk@lists.torproject.org>; Tue, 16 Sep 2014 16:52:31 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by mail.everdot.org (Postfix) with ESMTP id B0C1E9123145
 for <tor-talk@lists.torproject.org>; Tue, 16 Sep 2014 16:52:30 +0200 (CEST)
X-Virus-Scanned: amavisd-new at everdot.org
Received: from mail.everdot.org ([127.0.0.1])
 by localhost (everdot.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id m7g9QpZGzwii for <tor-talk@lists.torproject.org>;
 Tue, 16 Sep 2014 16:52:24 +0200 (CEST)
Received: from meilong (unknown [IPv6:2001:470:dc2e:2:8c3e:b768:7817:781])
 (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.everdot.org (Postfix) with ESMTPSA id 1FC8A91230D4
 for <tor-talk@lists.torproject.org>; Tue, 16 Sep 2014 16:52:24 +0200 (CEST)
Date: Tue, 16 Sep 2014 16:52:18 +0200
From: =?ISO-8859-1?B?1nl2aW5k?= Saether <oyvinds@everdot.org>
To: tor-talk@lists.torproject.org
Message-ID: <20140916165218.4ef95be6@meilong>
In-Reply-To: <54180D45.8070501@danielroskams.com>
References: <5417BD06.5020009@danielroskams.com> <5417F6AA.5030500@sky-ip.org>
 <54180D45.8070501@danielroskams.com>
X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.24; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Subject: Re: [tor-talk] Tor relay on home computer
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>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> What about bridges?

There is no big public list of bridges. They would have to look very
closely at you and your internet connection to find out that you are
running a bridge and if they are doing that then you have bigger
problems anyway.

Running a bridge on your home computer is totally safe and a great way
to help out. You should really do this.

Regarding your "Tor relay" question, it is like Moritz said: You can
run a Tor relay for years and years without any hint of
trouble AS LONG AS YOU DO NOT ALLOW PEOPLE TO EXIT. It is when you
allow people to _exit_ to the Internets the trouble starts because
people will send DMCA spam and other spam to your Internet Service
Provider because of your Tor exit node and this is where it gets very
risky. If you know what kind of moral values your ISP has then you can
likely guess how this will go down with them. Some view DMCA spam
e-mails as just that and others have a "6 strike system" where they
will just shut down your internets after 6 spam.

In short, just run a bridge and you'll do great or run a normal Tor
relay that does not allow exiting if your home connection is kind of
fast. Don't bother and just run a bridge if it is on ADSL or something
like that.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlQYTqUACgkQNBSJHnwv/KpZggCgut2L02ZVQZGfyteBsgvPJEyy
FRgAn1/0mr/9DYuMjxmXqYmjLh78YWU4
=z42V
-----END PGP SIGNATURE-----
-- 
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

