Delivery-Date: Tue, 16 Sep 2014 18:42:04 -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_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY
	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 172C11E0BA0;
	Tue, 16 Sep 2014 18:42:03 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 35A392A201;
	Tue, 16 Sep 2014 22:41:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 270EB2A17C
 for <tor-talk@lists.torproject.org>; Tue, 16 Sep 2014 22:41:55 +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 8e0Wnz3Momjs for <tor-talk@lists.torproject.org>;
 Tue, 16 Sep 2014 22:41:55 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id F34EE2653B
 for <tor-talk@lists.torproject.org>; Tue, 16 Sep 2014 22:41:54 +0000 (UTC)
Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified))
 by mx1.riseup.net (Postfix) with ESMTPS id 07B2652C2C;
 Tue, 16 Sep 2014 15:41:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1410907312; bh=ir9P3MLFm38g7J5yAvk7aQ9HgETOtSGxk/rTyGgCsBw=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=AM2vql2SNyoJb8S3MJq6Q9JBIKvj7745L8QHT1OgkO+PRISk0hyIqawYHtOQRL+fN
 euLg/TaXbTa3DQDJLcifPul2K7Ab5fhvpYXUsLaAFnVXBCNdQ/po/7I08YYes2iWQc
 m5uqJCx7l7MIX8TgNPiAxErmgC/p3fVbER+Ihjss=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: obx)
 with ESMTPSA id B879F22713
Date: Tue, 16 Sep 2014 22:42:05 +0000
From: obx <obx@riseup.net>
To: tor-talk@lists.torproject.org, contact@sectoor.de
Message-ID: <20140916224205.GO32501@badger>
References: <20140916205533.GL32501@badger>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20140916205533.GL32501@badger>
X-Virus-Scanned: clamav-milter 0.98.4 at mx1
X-Virus-Status: Clean
Subject: [tor-talk] sectoor issues [Was: Re:  Don't use sectoor]
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 apologize for my first mail, I should have waited to calm down a bit.

I've been looking into your website and figured out how to configure my
relay to not get listed.

I was allowing tcp/8000 since it's a common alternative http port. I'm
curious why you're listing tor exits that allow to exit to this port?

I'm currently waiting for the tor network to propagate my new exit
policy that shouldn't conflict with your listing.

Did you know there's an official TorDNSEL?

I hope you may understand my initial response since I was present in the
#support channel while some customers where not satisfied about this.

This was unprofessional and I'm very sorry.

Sincerly yours,
Jane Smith

On Tue, Sep 16, 2014 at 08:55:33PM +0000, obx wrote:
> Dear tor-talk, Dear sectoor,
> 
> I'm running a tor-exit at a small provider. Another customer at the same
> provider complained they got blacklisted by sectoor for operating a
> tor-exit. This customer doesn't run a tor server and didn't run a tor
> server in the past.
> 
> Hence, they got blacklisted as tor-exit.
> 
> I did some lookups and it looks like you banned the whole class C.
> 
> Why?
> 
> There's no need to "guess" since the list of tor exits is public
> information.
> 
> Please understand that is level of irresponsible management on your
> site, sectoor, can destroy the reputation of smaller providers.
> 
> I expect you fix this instantly.
> 
> -- 
> 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

