Delivery-Date: Fri, 04 Jul 2014 02:27:14 -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 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 235781E0C1B
	for <archiver@seul.org>; Fri,  4 Jul 2014 02:27:13 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E0DB22CE75;
	Fri,  4 Jul 2014 06:27:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C94C925EC6
 for <tor-talk@lists.torproject.org>; Fri,  4 Jul 2014 06:25:49 +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 JYaPjFHxk2oO for <tor-talk@lists.torproject.org>;
 Fri,  4 Jul 2014 06:25:47 +0000 (UTC)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com
 [IPv6:2607:f8b0:400e:c03::230])
 (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 411E82CF84
 for <tor-talk@lists.torproject.org>; Fri,  4 Jul 2014 06:25:36 +0000 (UTC)
Received: by mail-pa0-f48.google.com with SMTP id et14so1482055pad.35
 for <tor-talk@lists.torproject.org>; Thu, 03 Jul 2014 23:25:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lovetour.info; s=ggl;
 h=from:to:references:in-reply-to:subject:date:keywords:message-id
 :thread-index:content-language:mime-version:content-type;
 bh=e3bWfCSPgB7pW0lY0V9fsxxgRvedLsxCqKxjr3/2YzI=;
 b=XpSfCYwUr+/73wwfCewPM3N7OIt5wteetxUHSk9ZC2XUr2x7vlaovVQGhlMOIrxE46
 utaNGQ1O0OeZnY+ujUtaa/Eg6/mxZtHVIohcSwXP6YLIruzNUeC804ZZCfrkhVRxclDK
 eU5vcGvRCIogSO3XFTpuDH76o5DVigqbmp+no=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:references:in-reply-to:subject:date
 :keywords:message-id:thread-index:content-language:mime-version
 :content-type;
 bh=e3bWfCSPgB7pW0lY0V9fsxxgRvedLsxCqKxjr3/2YzI=;
 b=nFmOODO3nE1w2XfT6lANe9pXL2gjy/K4aDFkGF648in8qeMyMJwlKUx1j1sHtO/fyG
 8hfYLWXjbR0R5G0tISmd7S+EuCQNyd47yOXsfNgOU0Elf1pGf08ViBRqP07y/sElMJNv
 OcEyIbZfsVs6j/C0qFJ6/Ghusj+glM7n6M1TiumkpQdIj7gEPKLLztqKf8BGXMj8eQh4
 fxiZqLzkiAaqtGM/MqsJ/NF98zGqlhX2W6SJAVIN9ZmBubHnR00G90riJZacsd8omrRl
 ysaovOqff7mvrzbOF/X7bYthNYfX5QPTtjDR84dQ2UUQTPkfyWD3Znd2tJtdbGK0CC5i
 DDxg==
X-Gm-Message-State: ALoCoQmASK+fAlhEZpdeWVgtf+oarBhm/opk4DYyVDf7lVqFmMX/OQI/aydY78oKX/rf/QC+zJd/
X-Received: by 10.70.0.168 with SMTP id 8mr8373847pdf.34.1404454801524;
 Thu, 03 Jul 2014 23:20:01 -0700 (PDT)
Received: from lovemobile (70-36-130-148.dsl.dynamic.sonic.net.
 [70.36.130.148])
 by mx.google.com with ESMTPSA id zb2sm42998586pbb.45.2014.07.03.23.19.59
 for <tor-talk@lists.torproject.org>
 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Thu, 03 Jul 2014 23:20:00 -0700 (PDT)
From: "Asa Rossoff" <asa@lovetour.info>
To: <tor-talk@lists.torproject.org>
References: <53B2A1BC.9060109@riseup.net> <20140701140358.5b427aa8@ultrabook1>
 <53B3CDC3.9030701@riseup.net> <20140702122557.3bb59e44@ultrabook1>
 <53B56BAC.4030103@riseup.net>
In-Reply-To: <53B56BAC.4030103@riseup.net>
Date: Thu, 3 Jul 2014 23:19:57 -0700
Keywords: Mailing Lists
Message-ID: <042e01cf974f$fbd3dc50$f37b94f0$@info>
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac+WzxdHC1fF1RB+SUmBMQq6G0f7cgAfkiTQ
Content-Language: en-us
MIME-Version: 1.0
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] OTFC IRC issues - new Tor friendly IRC network?
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>

Hi Patrick,
I reported that issue to OFTC on their support channel and was told by an
operator that they believed they had a temporary Tor block in -place at the
moment, however, I was able to reconnect with a new ciruit (and before
identifying to services, got a Tor cloak, oddly enough).  I hit that issue
(same .at server noted in disconnect notice) just after 22:00 UTC on 2 July.
A new ciruit immediately resolved the problem for me.

It's possible that the OFTC operator was incorrect about what the issue
was.... If it persists, naming that server, I think it is up to them to fix
(and users to report).

I tried following the web page instrucions and reporting via email :), but
their mail exchange was over-zealous and bounced my message, which I also
reported.  The op said they have some unidentified/unresolved issues
communicating with certain mail servers.


As to whether 37lnq2veifl4kar7.onion is official, http://www.oftc.net/Tor/
only says "There is even a hidden service onion address that someone has
taken upon themselves to maintain, it is however not supported in any
official capacity by OFTC."

So, it is not official, and being thrid-party maintained, is certainly
routed through a normal exit node, so the issue with at least that exit node
at that time being rejected by OFTC should be independent of using the
hidden service to connect or not.

It is also extra-advisable to use SSL to connect, since there is an
additional man-in-the-middle running the hidden service... But of course SSL
should always be used anyway.

OFTC occasionally bans Tor connectinons to the best of their ability when a
lot of abuse is happenning, but most IRC servers seem to ban Tor connections
outright.  I'm happy enough personally with OFTC and it is suitable
considering their mission.  If we can suggest better ways for them to handle
abuse they might consider them, but it is a challenging issue on IRC as we
have seen on our own Tor channels lately.

One partial workaround is to use/also use a trusted IRC bouncer with a very
stable connection  to reduce the chances you will be disconnected and then
become subject to any ongoing ban.

Asa

> -----Original Message-----
> From: tor-talk [mailto:tor-talk-bounces@lists.torproject.org] On Behalf
> Of Patrick Schleizer
> Sent: Thursday, July 03, 2014 7:42 AM
> To: tor-talk@lists.torproject.org
> Subject: Re: [tor-talk] OTFC IRC issues - new Tor friendly IRC network?
> 
> BlueStar88:
> > On Wed, 02 Jul 2014 09:15:47 +0000
> > Patrick Schleizer <adrelanos@riseup.net> wrote:
> >
> >> BlueStar88:
> >>>
> >>> 37lnq2veifl4kar7.onion:6697 is up and running fine.
> >>
> >> Who runs that server? Inoffical one?
> >>
> >> I was more looking for a scalable, robust solution rather than
> >> individual quick fix.
> >
> > Hello Patrick,
> >
> > I don't know, who runs that service, but by using SSL, certificate
> verification and fingerprinting and optional OTR on top of that,
> there's nothing wrong with that one. Better having a stable unknown
> channel, than blocked official ones.
> >
> > That hidden service works well with my IRC-bouncer, which I use with
> "usewithtor" (torsocks wrapper). It seems to be quite robust to me.
> >
> > Well, your initial request was to have at least a temporary
> alternative.
> 
> Doesn't work either at the moment.
> 
> Closing Link: asteria.debian.or.at (No more connections from this host
> allowed.  See http://www.oftc.net/oftc/LimitExceptions for more info.)
> Disconnected (Remote host closed socket).
> 
> --
> 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

